All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	linux-kernel@vger.kernel.org,
	Darren Salt <linux@youmustbejoking.demon.co.uk>
Subject: Re: [PATCH 0/3] Fix rt28{6,7}0sta to use firmware loader
Date: Wed, 22 Apr 2009 16:13:31 -0700	[thread overview]
Message-ID: <20090422231331.GB16383@suse.de> (raw)
In-Reply-To: <1240222746.17844.35.camel@macbook.infradead.org>

On Mon, Apr 20, 2009 at 11:19:06AM +0100, David Woodhouse wrote:
> On Mon, 2009-04-13 at 19:24 -0700, Greg KH wrote:
> > On Tue, Apr 14, 2009 at 01:12:41AM +0100, Ben Hutchings wrote:
> > > On Sun, 2009-04-12 at 19:44 -0700, Greg KH wrote:
> > > > On Mon, Apr 13, 2009 at 03:33:12AM +0100, Ben Hutchings wrote:
> > > > > Greg,
> > > > > 
> > > > > The Ralink drivers rt2860sta, rt2870sta and rt3070sta contain non-free
> > > > > firmware which should be distributed separately.
> > > > 
> > > > Where is it now distributed?  I don't want to break people's machines
> > > > that were working before this patch is applied.
> > > 
> > > The canonical source is
> > > <http://www.ralinktech.com/ralink/Home/Support/Linux.html>
> > 
> > Yes, and that is where I got the code that is in the driver tree that
> > you are objecting to now :)
> 
> You shouldn't have done. We stopped including firmware for new wireless
> drivers _years_ ago. It's perfectly normal that users are expected to
> fetch the firmware separately (or their distribution does it for them).

Sorry, I should have added it to your tree in the beginning.

> > > The files are now also in the Debian repository for our firmware-nonfree
> > > package and in <http://git.decadent.org.uk/git/linux-firmware.git>.
> > > I've asked David Woodhouse to pull from that into his linux-firmware.git
> > > so that they get into other distros.
> 
> I'd be a lot happier with that having a signed-off-by from within
> Ralink, even though the licence is unambiguous. But I've pulled it
> anyway, this time. You can download the 'release' at
> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=snapshot;h=HEAD

Nice, thanks for doing this.

> (Still haven't really worked out what the best strategy for 'releases'
> is, given that people should just be using the latest version from the
> tree. Maybe an automatic git-archive from cron each day, if something's
> change from the previous day?)

Yes, that would be a good idea.  And a way to send an email to people
who are packaging this up for distros to know and go update them would
be good as well.

I have a firmware package now in the Gentoo tree, and am working on
making the SuSE one public (it's right now buried behind the firewall,
but will be pushed out soon.)

thanks,

greg k-h

      reply	other threads:[~2009-04-22 23:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13  2:33 [PATCH 0/3] Fix rt28{6,7}0sta to use firmware loader Ben Hutchings
2009-04-13  2:44 ` Greg KH
2009-04-14  0:12   ` Ben Hutchings
2009-04-14  2:24     ` Greg KH
2009-04-20 10:19       ` David Woodhouse
2009-04-22 23:13         ` 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=20090422231331.GB16383@suse.de \
    --to=gregkh@suse.de \
    --cc=ben@decadent.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@youmustbejoking.demon.co.uk \
    /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.