On Fri, Feb 6, 2009 at 4:40 AM, Leandro Dorileo <ldorileo@xxxxxxxxx> wrote: > Hi all > > Few days ago I wanted to understand a bit better udev, and started > reading its source code, and went to TODO file to see how I could > start contributing, and picket the line: "convert firmware.sh to C ". > In that regard I have some questions: > > 1 - there isn`t any a udev rule using firmware.sh in upstream source > code(I may have forgot something but a grep -r 'firmware.sh' in > rules.d didn`t show me any thing), do distributors set one? I also > couldn`t find one in fedora 10. There's a rule in extras/firmware/50-firmware.rules that gets installed along with firmware.sh. > 2 - who does set $DEVPATH, $FIRMWARE variables used in firmware.sh? The kernel sets them as part of the uevent, I believe. > 3 - why would be good "convert firmware.sh to C"? in TODO file this > line is followed by a "(?)" which makes me think it`s not well > discussed yet. ;) Speed? I don't know. It doesn't look like it does much beyond writing the firmware into a data entry in sysfs. -- Dan -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
