From: "Michael Büsch" <m@bues.ch>
To: b43-dev@lists.infradead.org
Subject: Question about IMCFGLO timeouts workaround
Date: Wed, 04 May 2011 14:48:57 +0200 [thread overview]
Message-ID: <1304513337.32096.6.camel@maggie> (raw)
In-Reply-To: <BANLkTimyDunC7anVitk=wCNJg5XN4B239A@mail.gmail.com>
On Wed, 2011-05-04 at 14:45 +0200, Rafa? Mi?ecki wrote:
> > Well, is REQTO and SERTO related to the PCI core only?
>
> No. There are two documented cases:
> 1) PCI (not e) cores rev < 5 need x32
> 2) Some BCM4311 and BCM4312 need 0x03
>
> This SSB_BUSTYPE_SSB with 0x53 is tricky for me and seems to be undocumented.
I'm not sure where it came from. It probably was there from the
very first b43 version on. I don't remember why I put it there.
Maybe you can find hints on the old (v3) specifications.
--
Greetings Michael.
prev parent reply other threads:[~2011-05-04 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 10:41 Question about IMCFGLO timeouts workaround Rafał Miłecki
2011-05-04 12:35 ` Michael Büsch
2011-05-04 12:45 ` Rafał Miłecki
2011-05-04 12:47 ` Rafał Miłecki
2011-05-04 12:48 ` Michael Büsch [this message]
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=1304513337.32096.6.camel@maggie \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.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).