From: "Saul St. John" <saul.stjohn@gmail.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org, Rafal Milecki <zajec5@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [RFC] bcma: add support for on-chip OTP memory used for SPROM storage
Date: Thu, 23 Feb 2012 20:42:02 -0600 [thread overview]
Message-ID: <20120224024202.GA30429@eris.garyseven.net> (raw)
In-Reply-To: <1330033977-5741-1-git-send-email-arend@broadcom.com>
On Thu, Feb 23, 2012 at 10:52:57PM +0100, Arend van Spriel wrote:
> Wireless Broadcom chips can have either their SPROM data stored
> on either external SPROM or on-chip OTP memory. Both are accessed
> through the same register space. This patch adds support for the
> on-chip OTP memory.
>
> Tested with:
> BCM43224 OTP and SPROM
> BCM4331 SPROM
> BCM4313 OTP
>
> This patch is in response so gmane article [1].
>
> [1] http://article.gmane.org/gmane.linux.kernel.wireless.general/85426
>
Tested-by: Saul St. John <saul.stjohn@gmail.com>
> Cc: Rafal Milecki <zajec5@gmail.com>
> Cc: Hauke Mehrtens <hauke@hauke-m.de>
> Cc: Larry Finger <Larry.Finger@lwfinger.net>
> Signed-off-by: Arend van Spriel <arend@broadcom.com>
> ---
> Determining the offset for OTP sprom data turned out to be
> easier as it boils down to reading a register. This change
> collides with patch posted by Hauke:
>
> bcma: add support for sprom not found on the device.
>
> Now working on changes in brcmsmac to start using the sprom
> data stored in struct bcma_bus. Feel free to comment this patch.
>
> Gr. AvS
This works for me. Do you still need to define BCMA_CC_SPROM_PCIE6?
next prev parent reply other threads:[~2012-02-24 4:44 UTC|newest]
Thread overview: 24+ 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 [this message]
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-01 21:26 ` Arend van Spriel
2012-03-01 21:42 ` Larry Finger
2012-03-01 21:56 ` Hauke Mehrtens
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=20120224024202.GA30429@eris.garyseven.net \
--to=saul.stjohn@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=hauke@hauke-m.de \
--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 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).