From: Harald Dunkel <harald.dunkel@t-online.de>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.27.1: install conflict about /lib/firmware
Date: Wed, 22 Oct 2008 21:35:01 +0200 [thread overview]
Message-ID: <48FF8065.9@t-online.de> (raw)
In-Reply-To: <48F7AB05.50103@msgid.tls.msk.ru>
Michael Tokarev wrote:
>
>> Wouldn't it be more consistent to put the firmware files in a
>> kernel specific directory, e.g. in /lib/firmware/2.6.27.1 or
>> /lib/modules/2.6.27.1/firmware ?
>
> No, because the firmware is not kernel-dependent, but device-dependent.
> It were deliberate choice.
>
This is not about some api incompatibility, but about a packaging
conflict. Even if each firmware file is kernel-independent, the
list of files is not. If I build and install *.rpm or *.deb files
for a new kernel version (probably with a changed set of modules),
then there is a high chance that the new package for /lib/\
firmware provides a new list of files, not suitable for another
kernel.
Regards
Harri
prev parent reply other threads:[~2008-10-22 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 18:47 2.6.27.1: install conflict about /lib/firmware Harald Dunkel
2008-10-16 20:58 ` Michael Tokarev
2008-10-17 18:13 ` Harald Dunkel
2008-10-22 19:35 ` Harald Dunkel [this message]
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=48FF8065.9@t-online.de \
--to=harald.dunkel@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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