On Fri, 27 Dec 2002 13:52:10 +1300 Jason <[EMAIL PROTECTED]> wrote: > Now that sounds like what might be going on in my case. How did you do > > it?? Step by step please ;) I find it strange that usbview sees it but > > the dynamic devfs entry is not created on plugin....
If you have the driver modules for the device compiled, new hotplug support and the correct modutils version all you have to do is # depmod -a Ehm... I have a self compiled linux sys using the new hotplug scheme http://linux-hotplug.sourceforge.net/ I dunno what mdk does about hotplugging (should be the same, tho) ... sorry ^^; Cut&paste from Hotplug site: Driver Information Database In order for the hotplug policy agent to be able to figure out what driver to load, it needs access to some kind of driver information database. Different kinds of busses provide different kinds of information, and need different driver selection algorithms. Maintaining those databases can be a problem in its own right. Linux delegates that problem to the driver developers, by persuading them to keep MODULE_DEVICE_TABLE entries up to date. The "modutils" package then exports that information in the form of text databases (modules.usbmap, modules.pcimap, and so forth) where it can be used to figure out what modules hold drivers for what devices. That same text database syntax is used for user mode drivers, using files like usb.handmap associating shell scripts with devices that had no kernel mode drivers. (If you're coming to Linux with much MS-Win32 background, you can think of that as analagous to the parts of the registry used to map bus-specific device IDs to drivers. One difference is that the IDs are part of the driver source and object code, rather than a separate registry info file. The Linux approach is simpler and less error prone.) ______________________________________________ So if you have the correct hotplug sys in place and it doesnt even try to load the modules, one possibility is that the driver do not list your device... Anyway more important than usbview is the log of hotplug agent when you plug in the device: it should say if it can find the device definition or not etc... Cheers -- Delio
