mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: Nick Craig-Wood <ncw1@axis.demon.co.uk>, Greg KH <greg@kroah.com>
Cc: Pavel Roskin <proski@gnu.org>, linux-kernel@vger.kernel.org
Subject: Re: Preferred way to load non-free firmware
Date: Wed, 26 Mar 2003 13:47:27 +0100	[thread overview]
Message-ID: <200303261347.27137.oliver@neukum.org> (raw)
In-Reply-To: <20030326104856.GA31375@axis.demon.co.uk>

Am Mittwoch, 26. März 2003 11:48 schrieb Nick Craig-Wood:
> On Tue, Mar 25, 2003 at 08:11:46PM -0800, Greg KH wrote:
> > > 7) Encode the firmware into a header file, add it to the driver and
> > > pretend that the copyright issue doesn't exist (like it's done in the
> > > Keyspan USB driver).
> >
> > Hey, that's the way I like doing this stuff :)
>
> If you do this the Debian kernel mainainers will mercilessly rip your
> non-free driver firmware from the standard Debian kernel.  At least
> that is what happened with the Keyspan :-(

That's their problem then. Or rather their users.
IMHO a maintainer's responsibility ends at kernel.org.
>From a technical point of view the firmware needs to be
in ram when you resume from sleep. If you don't care about
updating it, having it in the kernel image uses somewhat less
resources. So I'd say go for it.

	Regards
		Oliver



  reply	other threads:[~2003-03-26 12:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26  1:32 Pavel Roskin
2003-03-26  4:11 ` Greg KH
2003-03-26 10:48   ` Nick Craig-Wood
2003-03-26 12:47     ` Oliver Neukum [this message]
2003-03-26 13:52       ` Jeremy Jackson
2003-03-26 16:19         ` Oliver Neukum
2003-03-26 10:51 ` Erik Hensema
     [not found] <Pine.LNX.4.50.0303252007420.6656-100000@marabou.research.a tt.com>
2003-03-27  1:38 ` Max Krasnyansky

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=200303261347.27137.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncw1@axis.demon.co.uk \
    --cc=oliver@neukum.name \
    --cc=proski@gnu.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

all inboxes | Powered by JetHome®