From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev <b43-dev@lists.infradead.org>
Subject: [PATCH] b43: treat LCNXN-PHY as extra N-PHY devices
Date: Tue, 1 Jul 2014 12:13:18 +0200 [thread overview]
Message-ID: <53B289BE.10507@broadcom.com> (raw)
In-Reply-To: <CACna6rzisWW9YGQpOz9-PVD5bFg5ApzVfNSLbWmVJOYXgssqkQ@mail.gmail.com>
On 30-06-14 13:04, Rafa? Mi?ecki wrote:
> On 30 June 2014 12:54, Arend van Spriel <arend@broadcom.com> wrote:
>> 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).
>
> Err, I don't think so. Could you take a closer look at this? I'm
> pretty sure LCNXN is continuation of N.
You got me. I taken a closer look. It seems to stand for e'x'tended n.
There was separate phy code for it, but in recent code it seems to be
handled by n phy code. So you are right.
> Maybe you were thinking about LCN40? I don't know much about LCN40,
> maybe it's a variation of LCN?
Probably.
Gr. AvS
prev parent reply other threads:[~2014-07-01 10:13 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
2014-06-30 11:04 ` Rafał Miłecki
2014-07-01 10:13 ` Arend van Spriel [this message]
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=53B289BE.10507@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).