From: Michael Buesch <mb@bu3sch.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Larry Finger <larry.finger@lwfinger.net>,
Joseph Jezak <josejx@gentoo.org>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
John Linville <linville@tuxdriver.com>,
Bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH] bcm43xx: Fix code for spec changes of 2/7/2007
Date: Sat, 10 Feb 2007 06:55:50 +0100 [thread overview]
Message-ID: <200702100655.51495.mb@bu3sch.de> (raw)
In-Reply-To: <20070209213239.GA11650@srcf.ucam.org>
On Friday 09 February 2007 22:32, Matthew Garrett wrote:
> On Fri, Feb 09, 2007 at 01:26:25PM -0600, Larry Finger wrote:
>
> > My plan is to continue to maintain bcm43xx-SoftMAC for at least the BPHY and 4306 revisions even
> > after d80211 becomes the in-kernel driver. Of course, I hope that we will have found the killer bugs
> > by that time, and that maintenance will only require following kernel API changes.
>
> Just to make sure I'm understanding this correctly - does the v4
> firmware drop compatibility for older cards, or is it just that Broadcom
> dropped support in the driver at the same time as the firmware changed,
> and the new firmware will still also drive the old cards?
We don't know.
It's likely that old cards still work with v4 firmware, but we don't know and
it has to be tested.
Care to do so?
next prev parent reply other threads:[~2007-02-10 6:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 16:32 [PATCH] bcm43xx: Fix code for spec changes of 2/7/2007 Larry Finger
2007-02-09 17:11 ` Michael Buesch
2007-02-09 18:11 ` Larry Finger
2007-02-09 22:22 ` Joseph Jezak
2007-02-09 17:29 ` Michael Buesch
2007-02-09 18:21 ` Larry Finger
2007-02-09 18:48 ` Michael Buesch
2007-02-09 19:05 ` Joseph Jezak
2007-02-09 19:17 ` Michael Buesch
2007-02-09 19:55 ` Joseph Jezak
2007-02-09 20:30 ` Michael Buesch
2007-02-14 12:52 ` Johannes Berg
2007-02-14 19:13 ` Larry Finger
2007-02-14 19:26 ` Johannes Berg
2007-02-14 19:27 ` Johannes Berg
2007-02-14 21:52 ` Michael Buesch
2007-02-14 22:28 ` Larry Finger
2007-02-09 19:26 ` Larry Finger
2007-02-09 21:32 ` Matthew Garrett
2007-02-09 22:52 ` Martin Langer
2007-02-10 5:55 ` Michael Buesch [this message]
2007-02-10 12:57 ` Matthew Garrett
2007-02-27 17:00 ` Gavin McCullagh
2007-02-11 2:13 ` Joseph Jezak
2007-02-14 13:18 ` Johannes Berg
2007-02-14 21:40 ` Michael Buesch
2007-02-15 15:07 ` Johannes Berg
2007-02-15 15:13 ` Michael Buesch
2007-02-15 15:19 ` Johannes Berg
2007-02-15 16:51 ` Martin Langer
2007-02-15 16:53 ` Johannes Berg
2007-02-11 13:21 ` Johannes Berg
2007-02-09 18:45 ` Michael Buesch
2007-02-09 19:17 ` Joseph Jezak
2007-02-09 19:26 ` Michael Buesch
2007-02-09 19:58 ` Joseph Jezak
2007-02-09 22:24 ` Joseph Jezak
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=200702100655.51495.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=josejx@gentoo.org \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mjg59@srcf.ucam.org \
--cc=netdev@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).