[lkml]   [2005]   [Jun]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] bind and unbind drivers from userspace through sysfs
On Friday 24 June 2005 00:12, Greg KH wrote:
> Now that we have the internal infrastructure of the driver model
> reworked so the locks aren't so global and imposing, it's possible to
> bind and unbind drivers from devices from userspace with only a very
> tiny ammount of code.
> In reply to this email, are two patches, one that adds bind and one that
> adds unbind functionality. I've added these to my trees and should show
> up in the next -mm releases. Comments appreciated.
> Oh, and yes, we still need a way to add new device ids to drivers from
> sysfs, like PCI currently has. I'll be working on that next.

I think this is an overkill if you can do manual bind/unbind.

> Even so, with these two patches, people should be able to do things that
> they have been wanting to do for a while (like take over the what driver
> to what device logic in userspace, as I know some distro installers
> really want to do.)

I think bind/unbind should be bus's methods and attributes should be
created only if bus supports such operations. Some buses either have
or may need additional locking considerations and will not particularly
like driver core getting in the middle of things.

Btw, do we really need separate attributes for bind/unbind?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-06-25 06:48    [W:0.104 / U:11.928 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site