[Jeff Bailey] > I'm curious, though. The new hotplug seems to have the goal of > replacing discover. It may make sense to use that instead of > discover2 on 2.6 based systems (since it's likely that everyone will > want it anyway)
I've experienced some problems with hotplug earlier, as it is using the info in /lib/modules/<version>/modules.*map directly. If more than one module claim to support a given PCI id, it seem to pick any one of them. The tools having a separate hw database have an advantage here, where the maintainers can select which of these modules to use for a given PCI id. Is this problem solved with newer hotplug versions? Of course hotplug have a huge advantage using these maps directly, as the kernel module maintainers in effect is maintaining their HW database. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
