linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: John Daiker <daikerjohn@gmail.com>
Cc: Lennert Buytenhek <buytenh@wantstofly.org>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH,RFC] initial mwl8k driver for marvell topdog wireless
Date: Thu, 29 Jan 2009 19:49:13 -0500	[thread overview]
Message-ID: <1233276553.4085.51.camel@localhost.localdomain> (raw)
In-Reply-To: <49821FF1.4060200@gmail.com>

On Thu, 2009-01-29 at 13:30 -0800, John Daiker wrote:
> On 01/08/2009 09:23 AM, 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!
> >>      
> >
> > Would you guys mind if we split this up into an mwl8k core, and separate
> > mwl8335 and mwl8687 modules?  In starting to add at least firmware
> > upload for the 8335 last night, I realized that  most of the 8687
> > hardware access code won't work, because it's using DMA for passing the
> > firmware image to the card, while the 8335 uses many small writes to the
> > registers.  So I'd like to refactor the driver into those 3 distinct
> > modules instead.  Eventually there will probably be 8361 and 8362
> > modules as well once the TopDog N parts get added.
> >
> > Sound OK?  I'm working locally with git, but if I go too far it'll be a
> > ton of work to merge any changes you have.  Can we put this in a git
> > tree somewhere and all work from that while we wait for a merge?
> >
> > Dan
> >    
> Has any of this landed in a git repo yet?  I have an 8335 chip and would 
> love to help with testing, but need a place to find bits, first.

It's not in wireless-testing yet, because I don't think Lennert posted
an updated patchset addressing the comments from before Christmas.

Dan



  reply	other threads:[~2009-01-30  0: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
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 [this message]
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=1233276553.4085.51.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=buytenh@wantstofly.org \
    --cc=daikerjohn@gmail.com \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).