On Fri, 07 Sep 2007, David Brownell wrote: > > > For that matter, a *driver* should never create its own device node(s) > > > in the first place. Device creation belongs elsewhere, like as part of > > > platform setup or, for busses with integral enumeration support like > > > PCI or USB, bus glue. Linux is moving away from that legacy model. > > > > This assumes that we have a better bus than "platform" to dump drivers like > > thinkpad-acpi, hdaps, and a host of other host-specific stuff. > > I don't follow. If it's host-specific, then it's easy enough to > have a host-specific routine creating those platform devices. > A different host wouldn't call that routine.
We do that in the module that also provides the device driver. E.g. hdaps or thikpad-acpi will provide both the platform device (and register it), and the driver. > (Also, note that "platform", "host", and "board" are ambiguous. > In some contexts each is synonymous; in others, not. I avoid In this specific case I am talking about, they're not. ThinkPads are the host. The platform for a ThinkPad is either i386 or amd64. But there are many more hosts that are i386 or amd64 than ThinkPads, and the devices in my example are thinkpad-specific. I don't feel like drivers like hdaps, thinkpad-acpi, dock, bay, and many others really belong in the platform bus. But that's what happens right now. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
