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: Fri, 17 Oct 2008 20:13:46 +0200 [thread overview]
Message-ID: <48F8D5DA.4070209@t-online.de> (raw)
In-Reply-To: <48F7AB05.50103@msgid.tls.msk.ru>
Michael Tokarev wrote:
>
> Since 2.6.27, firmware binaries are placed into /lib/firmware
> directory. The reason is that firmware is not kernel-dependent.
> Or, rather, the firmware stored here is not kernel-dependent
> (when it is, it's stored in /lib/modules/$version/).
>
It would be nice if this could be configured. I wouldn't like
to have 2 directories to look for firmware files.
Actually I did not want to build any firmware drivers, but setting
CONFIG_PREVENT_FIRMWARE_BUILD did not work.
Regards
Harri
next prev parent reply other threads:[~2008-10-17 18:32 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 [this message]
2008-10-22 19:35 ` Harald Dunkel
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=48F8D5DA.4070209@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