From: "Arend van Spriel" <arend@broadcom.com>
To: "Saul St. John" <saul.stjohn@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"Rafał Miłecki" <zajec5@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 2/2] bcma: expose cc sprom to sysfs
Date: Fri, 17 Aug 2012 15:47:28 +0200 [thread overview]
Message-ID: <502E4B70.5090900@broadcom.com> (raw)
In-Reply-To: <20120816190616.GE6726@eris.garyseven.net>
On 08/16/2012 09:06 PM, Saul St. John wrote:
> On BCMA devices with a ChipCommon core of revision 31 or higher, the device
> SPROM can be accessed through CC core registers. This patch exposes the
> SPROM on such devices for read/write access as a sysfs attribute.
>
> Tested on a MacBookPro8,2 with BCM4331.
>
> Cc: Rafał Miłecki <zajec5@gmail.com>
> Cc: John W. Linville <linville@tuxdriver.com>
> Signed-off-by: Saul St. John <saul.stjohn@gmail.com>
Hi Saul,
I was still planning to come back to your reply on August 14. Just
wanted to reply to this patch as I still feel it is a bad thing to open
up the sprom as a whole. I can see the use-cases you mentioned as
useful, but maybe we can get a specific solution for that.
Gr. AvS
next prev parent reply other threads:[~2012-08-17 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 18:59 [PATCH 0/2] bcma: expose cc sprom for read/write in sysfs Saul St. John
2012-08-16 19:05 ` [PATCH 1/2] bcma: register cc core driver, device Saul St. John
2012-08-16 19:06 ` [PATCH 2/2] bcma: expose cc sprom to sysfs Saul St. John
2012-08-17 13:47 ` Arend van Spriel [this message]
2012-08-17 22:54 ` Saul St. John
2012-08-17 23:05 ` Saul St. John
2012-08-23 19:44 ` Rafał Miłecki
2012-08-23 20:53 ` Larry Finger
2012-08-24 8:37 ` 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=502E4B70.5090900@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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).