Messages in this thread | | | Date | Sat, 5 Jul 2008 02:01:24 -0400 | From | Bill Fink <> | Subject | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| |
On Sat, 5 Jul 2008, Henrique de Moraes Holschuh wrote:
> On Fri, 04 Jul 2008, Trent Piepho wrote: > > On Fri, 4 Jul 2008, Henrique de Moraes Holschuh wrote: > > > On Sat, 05 Jul 2008, Olivier Galibert wrote: > > >> Won't that break multiple kernel installs on any binary packaging > > >> system that cares about file collisions? Multiple kernel rpms > > >> providing the same /lib/firmware files would break things wouldn't > > >> they ? > > > > > > We will probably need per-kernel directories, exactly like what is done for > > > modules. And since there are (now) both kernel-version-specific, and > > > non-kernel-version-specific firmware, this means the firmware loader should > > > look first on the version-specific directory (say, /lib/firmware/$(uname > > > -r)/), then if not found, on the general directory (/lib/firmware). > > > > How about /lib/modules/`uname -r`/firmware > > I am fine with it, it certainly has a few advantages.
Why not put it in the same /lib/modules directory as the foo.ko kernel module itself? Then those who like to scp kernel modules around (which I've done myself on occasion) just need to learn to scp foo.* instead of foo.ko. Why replicate a separate /lib/modules/`uname -r`/firmware directory?
-Bill
| |