Messages in this thread | | | Date | Fri, 24 Jun 2005 23:05:53 -0400 | From | Bill Nottingham <> | Subject | Re: [RFC] bind and unbind drivers from userspace through sysfs |
| |
Greg KH (greg@kroah.com) said: > 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.)
Playing devils advocate, with this, the process flow is:
- kernel sees a new device - kernel sends hotplug event for bus with slot, address, vendor id, etc. - userspace loads a module based on that info <some sort of synchronization here waiting for driver to initialize> - userspace echos to sysfs to bind device - kernel sends hotplug device event - userspace creates device node, then continues with device
This looks: a) inefficient b) an awful lot like the PCMCIA model. Which... eww.
Bill - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |