linux-kernel - Re: RFC: install firmware in a kernel-dependent directory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.10.0902141410220.14911@asgard.lang.hm>
Date:	Sat, 14 Feb 2009 14:12:10 -0800 (PST)
From:	david@...g.hm
To:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>
cc:	Michael Riepe <michael.riepe@...glemail.com>,
	linux-kernel@...r.kernel.org, David Woodhouse <dwmw2@...radead.org>
Subject: Re: RFC: install firmware in a kernel-dependent directory

On Sun, 15 Feb 2009, Jaswinder Singh Rajput wrote:

> On Sat, Feb 14, 2009 at 5:55 PM, Michael Riepe
> <michael.riepe@...glemail.com> wrote:
>> Currently, make firmware_install puts all firmware blobs in
>> /lib/firmware. If you have several kernel versions installed, they will
>> overwrite each other's files, which may lead to problems if the blobs
>> eventually change. I think it would be better to use a separate
>> directory for every kernel version, like /lib/firmware/$(uname -r) or
>> /lib/modules/$(uname -r)/firmware (the latter is my favorite).
>>
>> In either case, only a minimal modification in /lib/udev/firmware.sh is
>> required to make it look in the new directory first.
>>
>> Comments?
>
> firmware version depends on hardware version not by kernel (software) version.

are you sure? different firmware could have different interfaces for the 
kernel to use.

I don't know if this is a problem in practice (I think I've heard of 
this), but there is no reason it couldn't be.

David Lang

> So /lib/firmware is absolutely OK.
>
> --
> JSR
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/