From: David Woodhouse <dwmw2@infradead.org>
To: david@lang.hm
Cc: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
Michael Riepe <michael.riepe@googlemail.com>,
linux-kernel@vger.kernel.org
Subject: Re: RFC: install firmware in a kernel-dependent directory
Date: Sat, 14 Feb 2009 22:13:29 +0100 [thread overview]
Message-ID: <1234646010.12772.0.camel@macbook.infradead.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0902141410220.14911@asgard.lang.hm>
On Sat, 2009-02-14 at 14:12 -0800, david@lang.hm wrote:
> are you sure? different firmware could have different interfaces for
> the kernel to use.
>
> I don't know if this is a problem in practice (I think I've heard of
> this), but there is no reason it couldn't be.
It would need different filenames then anyway (like sonames).
--
dwmw2
prev parent reply other threads:[~2009-02-14 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 12:25 RFC: install firmware in a kernel-dependent directory Michael Riepe
2009-02-14 19:02 ` 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 [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=1234646010.12772.0.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=david@lang.hm \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.riepe@googlemail.com \
/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.