From: Larry Finger <larry.finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Joseph Jezak <josejx@gentoo.org>, Michael Buesch <mb@bu3sch.de>,
linux-wireless@vger.kernel.org, Bcm43xx-dev@lists.berlios.de,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] bcm43xx: Fix code for spec changes of 2/7/2007
Date: Wed, 14 Feb 2007 13:13:41 -0600 [thread overview]
Message-ID: <45D35F65.7060001@lwfinger.net> (raw)
In-Reply-To: <1171457525.11116.19.camel@johannes.berg>
Johannes Berg wrote:
>> supported cards or a bug fix?
>
> Hmm. Same I guess, use the new check for new hw and the old check for
> old hw, i.e. assume it's the former and not a bug fix (until tested
> otherwise.)
>
> I think our best bet is to treat the older hw the same as the older
> driver does.
>
> A bigger problem, IMO, is that we'd have to support all the older
> microcode things which is a bit tricky since things in shm have moved a
> lot... Maybe we should find a third maintainer who has access to a
> couple of old cards :)
I've got a pair of BCM4306 rev 2 cards. One of them is certainly available. Its LEDS don't work
anymore, but the rest is functional.
Larry
next prev parent reply other threads:[~2007-02-14 19:13 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 [this message]
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
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=45D35F65.7060001@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=johannes@sipsolutions.net \
--cc=josejx@gentoo.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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).