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:35:32 +0200 [thread overview]
Message-ID: <1304512532.32096.4.camel@maggie> (raw)
In-Reply-To: <BANLkTi=bppqp9K50n-5d5MOW53-LvdbfyQ@mail.gmail.com>
On Wed, 2011-05-04 at 12:41 +0200, Rafa? Mi?ecki wrote:
> drivers/net/wireless/b43/main.c
> b43_imcfglo_timeouts_workaround
>
> Does it make sense to have here code:
> case SSB_BUSTYPE_SSB:
> tmp &= ~SSB_IMCFGLO_REQTO;
> tmp &= ~SSB_IMCFGLO_SERTO;
> tmp |= 0x53;
> break;
>
> Does SSB_BUSTYPE_SSB still have PCI core? I though SSB_BUSTYPE_SSB is
> some kind of native, not attached with PCI host.
Well, is REQTO and SERTO related to the PCI core only?
--
Greetings Michael.
next prev parent reply other threads:[~2011-05-04 12:35 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 [this message]
2011-05-04 12:45 ` Rafał Miłecki
2011-05-04 12:47 ` Rafał Miłecki
2011-05-04 12:48 ` 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=1304512532.32096.4.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).