public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mithlesh Thukral <mithlesh@linsyssoft.com>,
	Christopher Harrer <charrer@alacritech.com>
Subject: Re: Staging: sxg: Add support to download the firmware using request_firmware()
Date: Mon, 6 Apr 2009 08:26:56 -0700	[thread overview]
Message-ID: <20090406152656.GA25839@suse.de> (raw)
In-Reply-To: <20090406101026.04040c13@lxorguk.ukuu.org.uk>

On Mon, Apr 06, 2009 at 10:10:26AM +0100, Alan Cox wrote:
> > Firmware isn't "crap", it's needed by devices, and I don't see the
> > problem of distributing it within the kernel tree, especially when the
> > license of the firmware is just fine, like these files are.
> 
> For one firmware doesn't tie to the kernel release cycle so any
> serious distribution has to split the two packages apart even if the
> kernel community didn't.

So you are calling distros that don't do this "non-serious" now?  :)

What is the release cycle for this firmware tree?  And where is it
released at?

> For a second it keeps a lot of irrelevant, unreviewable enormous hex file
> changesets *off* the kernel lists and out of the git tree tracking.

git can handle this kind of thing trivially, that should not be an
issue.  And I have not posted firmware updates to the kernel lists
either, they probably just filter them out due to the size anyway.

So for now, as the majority of the distros don't have a separate
firmware package for the kernel, and there seems to not be any
"kernel-wide policy" yet in place, I'll stick to the in-tree location
for new drivers that need such a thing, as long as their firmware is
allowed to be proper redistributed.

thanks,

greg k-h

> 
> 
> Alan

      reply	other threads:[~2009-04-06 15:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200904051919.n35JJUUq031448@hera.kernel.org>
2009-04-06  0:41 ` Staging: sxg: Add support to download the firmware using request_firmware() David Woodhouse
2009-04-06  1:07   ` Greg KH
2009-04-06  1:19     ` David Woodhouse
2009-04-06  2:33       ` Greg KH
2009-04-06  9:10         ` Alan Cox
2009-04-06 15:26           ` Greg KH [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=20090406152656.GA25839@suse.de \
    --to=gregkh@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=charrer@alacritech.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mithlesh@linsyssoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox