From: "Michael Büsch" <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: [PATCH 2/2] ssb: Save sprom image for dump of device at alternate location
Date: Sun, 12 Dec 2010 17:12:19 +0100 [thread overview]
Message-ID: <1292170339.3572.11.camel@maggie> (raw)
In-Reply-To: <4D04F2AF.5080706@lwfinger.net> (sfid-20101212_170450_663695_3B8CD5F6)
On Sun, 2010-12-12 at 10:05 -0600, Larry Finger wrote:
> On 12/12/2010 09:38 AM, Michael B?sch wrote:
> >
> > So, do we actually make sure the wireless core is mapped while reading
> > SPROM from offset 0x800? I guess not and it just works by accident,
> > because the core is still mapped from a previous operation.
>
> I have core switching debug enabled on that box. When the SPROM is read, the
> ChipCommon core is mapped, and no other core has yet been selected.
Well, ok. Whatever core it is, it's coincidence that it is mapped.
I'd rather prefer an explicit mapping of the chipcommon before
the area is accessed. The chipcommon MMIO functions could probably
be used. That would be easiest. (16bit function does not exist, yet,
but is trivial to add).
--
Greetings Michael.
next prev parent reply other threads:[~2010-12-12 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 3:35 [PATCH 2/2] ssb: Save sprom image for dump of device at alternate location Larry Finger
2010-12-12 8:45 ` Michael Büsch
2010-12-12 15:34 ` Larry Finger
2010-12-12 15:38 ` Michael Büsch
2010-12-12 16:05 ` Larry Finger
2010-12-12 16:12 ` Michael Büsch [this message]
2010-12-12 9:03 ` Michael Büsch
2010-12-12 15:28 ` Larry Finger
2010-12-12 15:36 ` Michael Büsch
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=1292170339.3572.11.camel@maggie \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
/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).