From: Marcel Holtmann <marcel@holtmann.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Location of firmware files
Date: Tue, 22 Jun 2004 21:36:30 +0000 [thread overview]
Message-ID: <1087940190.4209.16.camel@pegasus> (raw)
In-Reply-To: <40ACDCE3.5040500@us.ibm.com>
Hi Marco,
> > Getting back to the following thread regarding the proper location
> > for firmware files:
> FYI, I applied this patch to the debian package, because some firmwares
> are needed before / is mounted.
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?
Regards
Marcel
-------------------------------------------------------
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 21:36 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 [this message]
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
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=1087940190.4209.16.camel@pegasus \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.