mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Greg KH <gregkh@suse.de>
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: Mon, 20 Apr 2009 11:19:06 +0100	[thread overview]
Message-ID: <1240222746.17844.35.camel@macbook.infradead.org> (raw)
In-Reply-To: <20090414022418.GA17760@suse.de>

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).
 
> > 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

(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?)

-- 
dwmw2


  reply	other threads:[~2009-04-20 10:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13  2:33 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 [this message]
2009-04-22 23:13         ` 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=1240222746.17844.35.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=ben@decadent.org.uk \
    --cc=gregkh@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome