public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: [QUESTION] 4331 support
Date: Mon, 22 Aug 2011 09:47:02 -0500	[thread overview]
Message-ID: <4E526BE6.3020504@lwfinger.net> (raw)
In-Reply-To: <1314023603.21805.75.camel@shinybook.infradead.org>

On 08/22/2011 09:33 AM, David Woodhouse wrote:
> On Mon, 2011-08-22 at 13:16 +0200, Maxime Vincent wrote:
>> I was wondering what the status of support for the 4331 wifi chipset was?
>> As I can see there's already quite some code for the 4331 chipset, but I
>> can't really make up from that if it's supposed to work or not, or maybe
>> partially?
>
> It is working well here, and has been for the last week or two.
>
> I'm not sure if all the patches are pushed upstream into the
> wireless-testing tree yet. Hopefully Rafa? will publish everything in a
> git tree.

To expand a little on what David wrote, the tree at wireless-testing is ahead of 
linux-next, and the published patches are even ahead of wireless-testing. The 
situation is changing rapidly, but 4331 support is quite near.

Larry

  reply	other threads:[~2011-08-22 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 11:16 [QUESTION] 4331 support Maxime Vincent
2011-08-22 14:33 ` David Woodhouse
2011-08-22 14:47   ` Larry Finger [this message]
2011-08-22 14:50     ` David Woodhouse
2011-08-27 12:08       ` Kalle Valo
2011-08-27 12:09         ` David Woodhouse
2011-08-27 12:15           ` Kalle Valo
2011-08-27 12:22             ` David Woodhouse
2011-08-22 20:50 ` Rafał Miłecki
2011-08-23 11:40   ` Maxime Vincent

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=4E526BE6.3020504@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.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