From: Kalle Valo <kvalo@codeaurora.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, Hauke Mehrtens <hauke@hauke-m.de>,
<stable@vger.kernel.org>
Subject: Re: [PATCH FIX] b43: fix support for 14e4:4321 PCI dev with BCM4321 chipset
Date: Mon, 08 Jun 2015 11:22:50 +0300 [thread overview]
Message-ID: <87fv62licl.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1433623559-25433-1-git-send-email-zajec5@gmail.com> ("Rafał Miłecki"'s message of "Sat, 6 Jun 2015 22:45:59 +0200")
Rafał Miłecki <zajec5@gmail.com> writes:
> It seems Broadcom released two devices with conflicting device id. There
> are for sure 14e4:4321 PCI devices with BCM4321 (N-PHY) chipset, they
> can be found in routers, e.g. Netgear WNR834Bv2. However, according to
> Broadcom public sources 0x4321 is also used for 5 GHz BCM4306 (G-PHY).
> It's unsure if they meant PCI device id, or "virtual" id (from SPROM).
> To distinguish these devices lets check PHY type (G vs. N).
>
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
> Cc: <stable@vger.kernel.org> # 3.16+
> ---
> Kalle: I'm aware it's quite late for a 4.1 fix, this bug was reported just
> today. I guess you can just take it for wireless-drivers-next and let stable
> guys handle it.
Yeah, I don't think this is critical enough to send this to 4.1. So
let's push this via wireless-drivers-next.
--
Kalle Valo
next prev parent reply other threads:[~2015-06-08 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 20:45 [PATCH FIX] b43: fix support for 14e4:4321 PCI dev with BCM4321 chipset Rafał Miłecki
2015-06-08 8:22 ` Kalle Valo [this message]
2015-06-08 11:33 ` 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=87fv62licl.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=hauke@hauke-m.de \
--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;
as well as URLs for NNTP newsgroup(s).