George Nychis <gnychis@...> writes: > > > If android hacked udev into the init deamon then you will have to > > modify the init daemon too but I doubt that they would have kept udev > > rules statically in the init daemon, so try to find the udev rules. > > > > I haven't been able to find any other udev rules on the Android > filesystem. I have done a ton of digging for any udev information on > Android, without any luck. I have asked on the Android mailing list, > we'll see how that goes. > > In the mean time, the compat_firmware.sh script is pretty straight > forward. My process on Android is continually monitoring the USB > devices connected, I could perform the same actions that > compat_firmware.sh does to dump the firmware into "/data" > > Thanks for the udev related pointers in compat-wireless! > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@... > More majordomo info at http://vger.kernel.org/majordomo-info.html > > I'm having a similar problem with another USB driver to a chipset that requires firmware. I have managed to compiler the driver using the compat-wireless method for the device but can not figure out where to put the firmware. George from the last post it seems you have a work around. Could you elaborate, give more details? ...dump firmware into "/data". Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
