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: <3f9a31f40902141115w27f20ecfk81213a21dbe1adbd@mail.gmail.com>
Date:	Sun, 15 Feb 2009 00:45:37 +0530
From:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>
To:	Michael Riepe <michael.riepe@...glemail.com>
Cc:	linux-kernel@...r.kernel.org, David Woodhouse <dwmw2@...radead.org>
Subject: Re: RFC: install firmware in a kernel-dependent directory

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.

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/