From: "Michael Büsch" <m@bues.ch>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Antonio Quartulli <antonio@meshcoding.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
b43-dev <b43-dev@lists.infradead.org>
Subject: [PATCH] b43: xmit: set 5 GHz bit depending on current band
Date: Tue, 20 May 2014 10:18:25 +0200 [thread overview]
Message-ID: <20140520101825.3d928446@wiggum> (raw)
In-Reply-To: <CACna6ryTSKim3ckZsJnE_1zrXW-JFabZSaJrLrOFL+JgXzLLjQ@mail.gmail.com>
On Tue, 20 May 2014 09:23:28 +0200
Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> You're probably right. It's just a bit historical, it matches bcm47xx
> specs, Broadcom's public code, Broadcom headers and probably their
> internal specs. That's why I didn't decide to really touch it, to
> avoid confusion when comparing specs with the code.
The thing is that the actual hardware bit is called GMODE.
I guess we could rename that variable and add a comment, if it's really an issue.
But not the #define for the hardware bit.
--
Michael.
----
Please use PGP/GPG encryption.
Key-ID: F532BE1D908D8B0E
--------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20140520/155208da/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Büsch" <m@bues.ch>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Antonio Quartulli <antonio@meshcoding.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
b43-dev <b43-dev@lists.infradead.org>
Subject: Re: [PATCH] b43: xmit: set 5 GHz bit depending on current band
Date: Tue, 20 May 2014 10:18:25 +0200 [thread overview]
Message-ID: <20140520101825.3d928446@wiggum> (raw)
In-Reply-To: <CACna6ryTSKim3ckZsJnE_1zrXW-JFabZSaJrLrOFL+JgXzLLjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
On Tue, 20 May 2014 09:23:28 +0200
Rafał Miłecki <zajec5@gmail.com> wrote:
> You're probably right. It's just a bit historical, it matches bcm47xx
> specs, Broadcom's public code, Broadcom headers and probably their
> internal specs. That's why I didn't decide to really touch it, to
> avoid confusion when comparing specs with the code.
The thing is that the actual hardware bit is called GMODE.
I guess we could rename that variable and add a comment, if it's really an issue.
But not the #define for the hardware bit.
--
Michael.
----
Please use PGP/GPG encryption.
Key-ID: F532BE1D908D8B0E
--------
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-20 8:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 6:46 [PATCH] b43: xmit: set 5 GHz bit depending on current band Rafał Miłecki
2014-05-20 6:46 ` Rafał Miłecki
2014-05-20 6:48 ` Antonio Quartulli
2014-05-20 6:48 ` Antonio Quartulli
2014-05-20 7:09 ` Rafał Miłecki
2014-05-20 7:09 ` Rafał Miłecki
2014-05-20 7:10 ` Antonio Quartulli
2014-05-20 7:10 ` Antonio Quartulli
2014-05-20 7:23 ` Rafał Miłecki
2014-05-20 7:23 ` Rafał Miłecki
2014-05-20 8:18 ` Michael Büsch [this message]
2014-05-20 8:18 ` Michael Büsch
2014-05-20 8:24 ` Rafał Miłecki
2014-05-20 8:24 ` Rafał Miłecki
2014-05-20 7:27 ` [PATCH V2] " Rafał Miłecki
2014-05-20 7:27 ` Rafał Miłecki
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=20140520101825.3d928446@wiggum \
--to=m@bues.ch \
--cc=antonio@meshcoding.com \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.