From: "Michael Büsch" <mb@bu3sch.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>,
b43-dev <b43-dev@lists.infradead.org>
Subject: Notes on ssb specs and implementation
Date: Mon, 14 Feb 2011 23:01:17 +0100 [thread overview]
Message-ID: <1297720877.5683.3.camel@maggie> (raw)
In-Reply-To: <AANLkTinjDMSCqxWbAfjZO_JkfBZeRoAZOG5Pxvf1v8Xr@mail.gmail.com> (sfid-20110214_205318_109392_FFFFFFFFAA87CB50)
On Mon, 2011-02-14 at 20:51 +0100, Rafa? Mi?ecki wrote:
> W dniu 9 lutego 2011 21:17 u?ytkownik Michael B?sch <mb@bu3sch.de> napisa?:
> > On Wed, 2011-02-09 at 21:00 +0100, Rafa? Mi?ecki wrote:
> >> Michael: was there any reasons why we didn't implement some parts of
> >> core-disabling code?
> >
> > The function are complete as of latest reverse engineering efforts.
> > Broadcom added stuff, if they do more stuff in latest code.
>
> Nothing has changed in specs since 2006:
> http://bcm-v4.sipsolutions.net/Backplane?action=info
> For some reason routines that were present even in 2006 was not implemented.
Well, so the function was implemented prior to 2006. Which doesn't
surprise me. It was one of the first ones.
> I've just written missing parts,
May I see them?
> tested and it still does not work :|
> The only advantage discovered so far is that ssb detects sth is wrong
> with IM state:
> [ 2661.449647] ssb: Timeout waiting for bitmask 01800000 on register
> 0F90 to clear.
>
> I can see wl experiencing the same problems after loading b43. It
> reads 0xf90 dozen of times in a row.
And that's the thing why I always avoid touching that function.
There's so much magic going on, so that completely weird things happen
all the time. :D
--
Greetings Michael.
next prev parent reply other threads:[~2011-02-14 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 20:00 Notes on ssb specs and implementation Rafał Miłecki
2011-02-09 20:17 ` Michael Büsch
2011-02-14 19:51 ` Rafał Miłecki
2011-02-14 22:01 ` Michael Büsch [this message]
2011-02-14 22:32 ` Rafał Miłecki
2011-02-14 22:52 ` Michael Büsch
2011-02-14 23:02 ` Rafał Miłecki
2011-02-14 23:08 ` 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=1297720877.5683.3.camel@maggie \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--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).