b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Question about IMCFGLO timeouts workaround
Date: Wed, 4 May 2011 14:47:18 +0200	[thread overview]
Message-ID: <BANLkTimpbob5u+GNRKstE=mnfmkeo74ZDw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimyDunC7anVitk=wCNJg5XN4B239A@mail.gmail.com>

W dniu 4 maja 2011 14:45 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?:
> 1) PCI (not e) cores rev < 5 need x32

This one is performed on PCI core


> 2) Some BCM4311 and BCM4312 need 0x03

This one is performed on 80211 core.


> This SSB_BUSTYPE_SSB with 0x53 is tricky for me and seems to be undocumented.

Not sure about this one. We currently perform this on 80211 core, but
this is in group with 0x32, which we were performing incorrectly on
80211 core.

-- 
Rafa?

  reply	other threads:[~2011-05-04 12:47 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 [this message]
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='BANLkTimpbob5u+GNRKstE=mnfmkeo74ZDw@mail.gmail.com' \
    --to=zajec5@gmail.com \
    --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).