All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Dan Williams <dcbw@redhat.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Lennert Buytenhek <buytenh@wantstofly.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH,RFC] initial mwl8k driver for marvell topdog wireless
Date: Tue, 16 Dec 2008 01:50:39 -0800	[thread overview]
Message-ID: <20081216095039.GA6358@tesla> (raw)
In-Reply-To: <1229449041.7307.49.camel@localhost.localdomain>

On Tue, Dec 16, 2008 at 09:37:21AM -0800, Dan Williams wrote:
> On Tue, 2008-12-16 at 11:16 -0500, John W. Linville wrote:
> > On Tue, Dec 16, 2008 at 11:10:06AM -0500, Dan Williams wrote:
> > > On Tue, 2008-12-16 at 03:55 +0100, Lennert Buytenhek wrote:
> > > > Hi all,
> > > >
> > > > Attached is an initial version of the mwl8k driver for Marvell 88w8xxx
> > > > PCI/PCIe wireless parts (against 2.6.27.1).  This version was written
> > > > and tested against the 88w8687 (802.11b/g), but it shouldn't be hard to
> > > > extend the support to other parts in the 8xxx series, since the firmware
> > > > interface is very similar between parts.
> > > >
> > > > There's an occasional timeout warning with mwl8k_stop(), and hardware
> > > > crypto is still a work-in-progress, but other than that it looks pretty
> > > > stable.
> > > >
> > > > Feedback appreciated!
> > >
> > > Oooh, thanks for the Christmas present.  Just in time for the holidays.
> > > Is there a git repo somewhere that we could all base off of, so we don't
> > > have to deal with patches to patches to patches until it gets into
> > > wireless-testing?
> >
> > I wouldn't worry too much about that.  The better questions is where
> > do we get firmware?
> 
> I believe I can post it.  Marvell recently changed the license terms on
> at least some of their firmware to be comparable to other freely
> available firmware (like Intel's).  Unfortunately you must have an
> extranet account to get it (they are working on fixing this too) but
> once you have it, the firmware blobs themselves are under a nice
> license.  I'll try to get something together today.

The right thing to do (tm) would be to post the firmware along with a
friendly license by the vendor to the linux-firmware git tree.

Lennert is this possible?

  Luis

  reply	other threads:[~2008-12-16 17:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16  2:55 [PATCH,RFC] initial mwl8k driver for marvell topdog wireless Lennert Buytenhek
2008-12-16  3:13 ` Lennert Buytenhek
2008-12-16 10:36   ` Johannes Berg
2008-12-16 16:10 ` Dan Williams
2008-12-16 16:16   ` John W. Linville
2008-12-16 17:37     ` Dan Williams
2008-12-16  9:50       ` Luis R. Rodriguez [this message]
2008-12-16 19:10         ` Dan Williams
2008-12-16 17:51       ` Stefanik Gábor
2009-02-25  2:37   ` Lennert Buytenhek
2008-12-18 19:35 ` Johannes Berg
2009-02-25  2:34   ` Lennert Buytenhek
2009-02-27 17:27     ` Johannes Berg
2009-02-28  3:37       ` Lennert Buytenhek
2009-01-06 12:57 ` Jan Kiszka
2009-02-25  2:47   ` Lennert Buytenhek
2009-01-08 17:23 ` Dan Williams
2009-01-29 21:30   ` John Daiker
2009-01-30  0:49     ` Dan Williams
2009-02-12  3:18       ` John Daiker

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=20081216095039.GA6358@tesla \
    --to=lrodriguez@atheros.com \
    --cc=buytenh@wantstofly.org \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.