> > > > * Add this udev rule: > > SUBSYSTEM=="firmware", ACTION=="add", RUN+="/lib/udev/hotplug-script" > > > > * Check that there aren't other 'firmware' udev rules to get in the > > way. > > Hm, don't do that, all "modern" distros will not do firmware loading > through udev anymore, so please don't try to add it back in. The kernel > handles the loading of the firmware directly, with no need to call any > usermodehelper program at all. > > > * Add your firmware files to /usr/lib/hotplug/firmware/ or change that > > path in hotplug-script to point to where your firmware files. > > > > The default hotplug-script doesn't do anything special (that the kernel > > couldn't do by itself). What's great is that it could call another > > script that adds headers or does whatever other special un-gzipping or > > other massaging that the firmware image needs before it gets loaded. > > Only if you need to do something "special" like this could it justify > not using the in-kernel firmware loader. Also note that I think future > versions of udev will have the udev firmware loader removed entirely, so > watch out for that. >
Hi Greg, Thanks for the heads-up on the direction the firmware class is taking. Well, that's kind of disappointing. I was just getting excited about how flexible the firmware class currently is. In the simpler fpga use cases, using the in-kernel loader to load static raw images would be great. But we are really excited about exploiting the possibilities that fpga's give in terms of reconfiguration and partial reconfiguration on the fly, so we will be needing to do 'special' things (unpacking images, stripping headers, lots of stuff that userspace would better for and that we wouldn't want to put into the kernel). I hope that we can arrive at a framework with a unified interface that suites this. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
