From: Larry Finger <Larry.Finger@lwfinger.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Saul St. John" <saul.stjohn@gmail.com>,
Rafal Milecki <zajec5@gmail.com>
Subject: Re: [RFC] bcma: add support for on-chip OTP memory used for SPROM storage
Date: Thu, 01 Mar 2012 15:42:38 -0600 [thread overview]
Message-ID: <4F4FED4E.2010000@lwfinger.net> (raw)
In-Reply-To: <4F4FE989.3090108@broadcom.com>
On 03/01/2012 03:26 PM, Arend van Spriel wrote:
>
> SPEX(board_rev, SSB_SPROM8_BOARDREV, ~0, 0);
>
> SPEX(txpid2g[0], SSB_SPROM4_TXPID2G01, SSB_SPROM4_TXPID2G0,
> SSB_SPROM4_TXPID2G0_SHIFT);
> SPEX(txpid2g[1], SSB_SPROM4_TXPID2G01, SSB_SPROM4_TXPID2G1,
> SSB_SPROM4_TXPID2G1_SHIFT);
>
> The attributes txpid2g that are filled here are deprecated for srom revision 8.
> Is b43 using these fields for boards with srom rev 8?
>
> I propose to move to BCMA having its own sprom structure definition. Srom
> revision 10 is upcoming and it does only apply to BCMA-based cards.
If there will be SPROM revisions that are not appropriate for SSB, then BCMA
should likely have its own definition.
Those attributes that are deprecated for Rev 8 are there because we had no way
to know that they were being eliminated. That was not apparent when doing the
reverse engineering.
Larry
next prev parent reply other threads:[~2012-03-01 21:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 21:52 [RFC] bcma: add support for on-chip OTP memory used for SPROM storage Arend van Spriel
2012-02-24 2:42 ` Saul St. John
2012-02-24 9:55 ` Arend van Spriel
2012-02-24 7:52 ` Rafał Miłecki
2012-02-24 10:15 ` Arend van Spriel
2012-02-24 10:39 ` Arend van Spriel
2012-02-24 10:58 ` Johannes Berg
2012-02-24 11:18 ` Arend van Spriel
2012-02-25 12:52 ` Hauke Mehrtens
2012-02-25 14:29 ` Rafał Miłecki
2012-02-27 10:12 ` Arend van Spriel
2012-02-28 20:11 ` Hauke Mehrtens
2012-03-01 14:12 ` Arend van Spriel
2012-03-01 14:35 ` Hauke Mehrtens
2012-03-01 15:16 ` Arend van Spriel
2012-03-01 16:14 ` Hauke Mehrtens
2012-03-03 22:44 ` Rafał Miłecki
2012-03-05 9:16 ` Arend van Spriel
2012-03-06 8:52 ` Rafał Miłecki
2012-03-06 12:26 ` Arend van Spriel
2012-03-06 12:26 ` Arend van Spriel
2012-03-01 21:26 ` Arend van Spriel
2012-03-01 21:42 ` Larry Finger [this message]
2012-03-01 21:56 ` Hauke Mehrtens
2012-03-02 10:39 ` Arend van Spriel
2012-03-02 10:39 ` 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=4F4FED4E.2010000@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=saul.stjohn@gmail.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 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.