b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Cc: b43-dev@lists.infradead.org
Subject: [PATCH] b43: treat LCNXN-PHY as extra N-PHY devices
Date: Mon, 30 Jun 2014 12:54:03 +0200	[thread overview]
Message-ID: <53B141CB.7010000@broadcom.com> (raw)
In-Reply-To: <1404071205-12568-1-git-send-email-zajec5@gmail.com>

On 29-06-14 21:46, Rafa? Mi?ecki wrote:
> LCNXN is simply a continuation of N, e.g. code handling LCNXN revs 0 and
> 1 is mostly the same as for N-PHY revs 7+.

Hi Rafa?,

LCNXN is actually a LCN phy with 2 streams (mimo).

Regards,
Arend

> Signed-off-by: Rafa? Mi?ecki <zajec5@gmail.com>
> ---
>  drivers/net/wireless/b43/main.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/net/wireless/b43/main.c b/drivers/net/wireless/b43/main.c
> index 3e4333c..0b1aac4 100644
> --- a/drivers/net/wireless/b43/main.c
> +++ b/drivers/net/wireless/b43/main.c
> @@ -4331,6 +4331,13 @@ static int b43_phy_versioning(struct b43_wldev *dev)
>  	analog_type = (tmp & B43_PHYVER_ANALOG) >> B43_PHYVER_ANALOG_SHIFT;
>  	phy_type = (tmp & B43_PHYVER_TYPE) >> B43_PHYVER_TYPE_SHIFT;
>  	phy_rev = (tmp & B43_PHYVER_VERSION);
> +
> +	/* LCNXN is continuation of N which run out of revisions */
> +	if (phy_type == B43_PHYTYPE_LCNXN) {
> +		phy_type = B43_PHYTYPE_N;
> +		phy_rev += 16;
> +	}
> +
>  	switch (phy_type) {
>  #ifdef CONFIG_B43_PHY_G
>  	case B43_PHYTYPE_G:
> 

  reply	other threads:[~2014-06-30 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 19:46 [PATCH] b43: treat LCNXN-PHY as extra N-PHY devices Rafał Miłecki
2014-06-30 10:54 ` Arend van Spriel [this message]
2014-06-30 11:04   ` Rafał Miłecki
2014-07-01 10:13     ` Arend van Spriel

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=53B141CB.7010000@broadcom.com \
    --to=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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).