From: Michael Riepe <michael.riepe@googlemail.com>
To: linux-kernel@vger.kernel.org
Subject: RFC: install firmware in a kernel-dependent directory
Date: Sat, 14 Feb 2009 13:25:28 +0100 [thread overview]
Message-ID: <4996B838.2070205@googlemail.com> (raw)
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?
--
Michael "Tired" Riepe <michael.riepe@googlemail.com>
X-Tired: Each morning I get up I die a little
next reply other threads:[~2009-02-14 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 12:25 Michael Riepe [this message]
2009-02-14 19:02 ` RFC: install firmware in a kernel-dependent directory Robert Hancock
2009-02-14 19:15 ` Jaswinder Singh Rajput
2009-02-14 20:00 ` Michael Riepe
2009-02-14 20:50 ` David Woodhouse
2009-02-14 22:12 ` david
2009-02-14 21:13 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4996B838.2070205@googlemail.com \
--to=michael.riepe@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox