From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: [RFC/RFT] ssb: resolve alternate SPROM offset for 14e4:4315
Date: Fri, 7 May 2010 00:44:56 +0200 [thread overview]
Message-ID: <201005070044.56589.mb@bu3sch.de> (raw)
In-Reply-To: <4BE2C009.8020002@lwfinger.net>
On Thursday 06 May 2010 15:11:37 Larry Finger wrote:
> Is it OK to read the chipcommon capabilities here?
Yeah. That register exists on all revisions.
Only add stuff to ssb_bus_scan that really _needs_ to be done that early.
Anything else should be done later.
--
Greetings, Michael.
WARNING: multiple messages have this Message-ID (diff)
From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT] ssb: resolve alternate SPROM offset for 14e4:4315
Date: Fri, 7 May 2010 00:44:56 +0200 [thread overview]
Message-ID: <201005070044.56589.mb@bu3sch.de> (raw)
In-Reply-To: <4BE2C009.8020002@lwfinger.net>
On Thursday 06 May 2010 15:11:37 Larry Finger wrote:
> Is it OK to read the chipcommon capabilities here?
Yeah. That register exists on all revisions.
Only add stuff to ssb_bus_scan that really _needs_ to be done that early.
Anything else should be done later.
--
Greetings, Michael.
next prev parent reply other threads:[~2010-05-06 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 5:00 [RFC/RFT] ssb: resolve alternate SPROM offset for 14e4:4315 Larry Finger
2010-05-06 8:45 ` Mark Huijgen
2010-05-06 9:53 ` Michael Buesch
2010-05-06 9:53 ` Michael Buesch
2010-05-06 10:01 ` Michael Buesch
2010-05-06 10:01 ` Michael Buesch
2010-05-06 13:11 ` Larry Finger
2010-05-06 13:11 ` Larry Finger
2010-05-06 22:44 ` Michael Buesch [this message]
2010-05-06 22:44 ` Michael Buesch
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=201005070044.56589.mb@bu3sch.de \
--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 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.