From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Location of firmware files
Date: Tue, 22 Jun 2004 23:09:58 +0000 [thread overview]
Message-ID: <20040622230958.GA12771@kroah.com> (raw)
In-Reply-To: <40ACDCE3.5040500@us.ibm.com>
On Wed, Jun 23, 2004 at 12:02:26AM +0200, Marcel Holtmann wrote:
> Hi Brian,
>
> > > as I already argued I am not really happy with having two locations for
> > > the firmware files. Lets agree on one. We have /lib/modules/ for our
> > > kernel modules and so I think /lib/firmware/ is also fine. What does the
> > > LSB says about it?
> >
> > The LSB doesn't say much in this respect. I had a discussion on this a while
> > back on the FHS list:
> >
> > http://sourceforge.net/mailarchive/message.php?msg_idh01284
> >
> > The result of this discussion suggested placing them in somewhere in /lib.
> > /lib/drivername was suggested, but it was brought up outside this thread
> > that this could cause problems for devices that can use multiple drivers,
> > such as some scsi devices.
>
> using something like /lib/drivername will cause much more troubles than
> it will help us. So I think /lib/firmware is a nice place to keep the
> firmware files. The Debian packages already did it this way and so I
> think we should go this way. Any arguments against it?
No argument from me. We can get the LSB to add this after we implement
it (they document current usage.)
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-06-22 23:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 16:29 Location of firmware files Brian King
2004-05-20 16:53 ` Marco d'Itri
2004-05-20 17:19 ` Marcel Holtmann
2004-05-20 17:25 ` Marco d'Itri
2004-05-20 18:16 ` Marcel Holtmann
2004-06-22 20:50 ` Brian King
2004-06-22 21:17 ` Marco d'Itri
2004-06-22 21:36 ` Marcel Holtmann
2004-06-22 21:51 ` Brian King
2004-06-22 22:02 ` Marcel Holtmann
2004-06-22 22:27 ` Brian King
2004-06-22 22:37 ` Marcel Holtmann
2004-06-22 23:09 ` Greg KH [this message]
2004-06-23 8:14 ` Marcel Holtmann
2004-09-20 21:23 ` Greg KH
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=20040622230958.GA12771@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).