public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Jonas Gorski <jogo@openwrt.org>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	b43-dev <b43-dev@lists.infradead.org>,
	stable@vger.kernel.org
Subject: [PATCH][FIX][RESEND] b43: fix support for 5 GHz only BCM43228 model
Date: Tue, 03 Mar 2015 17:44:25 +0200	[thread overview]
Message-ID: <87fv9m84rq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAOiHx==ZbVCsymBFhn60nBU2-gHU2HPdp1T9xdZpK9OVjAzFUw@mail.gmail.com> (Jonas Gorski's message of "Tue, 3 Mar 2015 16:38:54 +0100")

Jonas Gorski <jogo@openwrt.org> writes:

> On Tue, Mar 3, 2015 at 4:05 PM, Kalle Valo <kvalo@codeaurora.org> wrote:
>>> RESEND: It seems patchwork didn't catch my patch. Trying again.
>>
>> Odd, I still don't see it in patchwork. I wonder what caused that?
>
> I also see it neither in my b43-dev nor linux-wireless archives, nor
> does google find it (only your reply).

Ok, that explains why patchwork didn't catch it (it scans patches from
the linux-wireless mailing list). I already applied the patch to
wireless-drivers.git but I would appreciate if people would still review
it:

commit 0ff66cffde47de51c155ebdd2356403276c04cc4
Author: Rafa? Mi?ecki <zajec5@gmail.com>
Date:   Mon Mar 2 17:18:55 2015 +0100

    b43: fix support for 5 GHz only BCM43228 model
    
    It was incorrectly detected as 2 GHz device.
    
    Signed-off-by: Rafa? Mi?ecki <zajec5@gmail.com>
    Cc: stable at vger.kernel.org # 3.17+
    Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

diff --git a/drivers/net/wireless/b43/main.c b/drivers/net/wireless/b43/main.c
index ccbdb05b28cd..75345c1e8c34 100644
--- a/drivers/net/wireless/b43/main.c
+++ b/drivers/net/wireless/b43/main.c
@@ -5370,6 +5370,7 @@ static void b43_supported_bands(struct b43_wldev *dev, bool *have_2ghz_phy,
 	case 0x432a: /* BCM4321 */
 	case 0x432d: /* BCM4322 */
 	case 0x4352: /* BCM43222 */
+	case 0x435a: /* BCM43228 */
 	case 0x4333: /* BCM4331 */
 	case 0x43a2: /* BCM4360 */
 	case 0x43b3: /* BCM4352 */


-- 
Kalle Valo

  reply	other threads:[~2015-03-03 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1424103816-10566-1-git-send-email-zajec5@gmail.com>
     [not found] ` <1425313135-28225-1-git-send-email-zajec5@gmail.com>
2015-03-03 15:05   ` [PATCH][FIX][RESEND] b43: fix support for 5 GHz only BCM43228 model Kalle Valo
2015-03-03 15:38     ` Jonas Gorski
2015-03-03 15:44       ` Kalle Valo [this message]
2015-03-03 15:49         ` Jonas Gorski
2015-03-03 15:52           ` Jonas Gorski
2015-03-03 16:00             ` Kalle Valo

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=87fv9m84rq.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=b43-dev@lists.infradead.org \
    --cc=jogo@openwrt.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=zajec5@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox