On Mon, May 16, 2011 at 2:09 PM, George Nychis <gnychis@xxxxxxxxx> wrote: >> compat-wireless uses a new module called compat_firmware so you need a >> respective new udev rule for it, it uses the same path for firmware >> though so you just need to slap on the right udev rule. >> > > Thanks for the response, Luis! > > I'm not a udev expert, and my problem might be slightly > Android-dependent, so feel free to punt the conversation at any point. > > I've tried setting up a set of rules on my Android device to handle > this situation. ÂThere was no /etc/udev or anything related, before I > created them. ÂI created a udev.conf and a default set of rules, and > then migrated the compat_firmware rules on over. ÂBut, udev seems to > be ignoring everything. > > Unfortunately, there's not a lot documented in terms of udev on > Android. ÂI did manage to find a little bit of information on a page > that's actually about root exploits on Android: > http://intrepidusgroup.com/insight/2010/09/android-root-source-code-looking-at-the-c-skills/ > > Apparently one of them is a udev exploit, and the author mentions that: > "Android does not have a separate udev executable and process link > [like] on standard Linux deployments. However, large portions of the > udev code have been moved into the init daemon." > > I'm not sure if this customization of udev or migration of it into the > init daemon is affecting anything here. > > Is there any simple backwards compatible way of bypassing > compat_firmware? ÂIf not, I will dig up some of the older > compat-wireless code to try and remedy the problem and get around > compat_firmware. 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. Luis -- 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
