On Sat, 2012-05-12 at 20:58 -0400, Walter Dnes wrote: > There's documentation at > http://git.busybox.net/busybox/plain/docs/mdev.txt which mentions... > > Mdev has two primary uses: initial population and dynamic updates. > It goes on to give some examples. Is this what you're looking for?
Kind of, but it didn't explain how to know what device names would be created by mdev. For USB WiFi my first thought was to use net.* for the device, but that didn't work because mdev is just creating the USB device generically. So I had to look at the usb device mdev creates and then use lsusb to grab the product/vendor IDs and match those up with a custom config file to know which kernel module to load. BTW, this worked for me. The driver is loaded properly at boot time. It also means that to support other wifi devices, I just need to migrate their product/vendor IDS from usb.ids and match them up with their kernel modules. -- Michael J. Hammel <[email protected]> _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
