b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev <b43-dev@lists.infradead.org>,
	linux-wireless@vger.kernel.org,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Michael Buesch <mb@bu3sch.de>
Subject: b43/SSB: SPROM revision problem
Date: Fri, 22 Oct 2010 14:45:23 +0200	[thread overview]
Message-ID: <AANLkTinwXMcP3F=Py4S2sjJVpiRsXpVndXP-W55EAsBT@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikVug2RFWFkv7_dJn_jn+NZAyTR2wMoeDzC2-WG@mail.gmail.com>

W dniu 22 pa?dziernika 2010 14:41 u?ytkownik Rafa? Mi?ecki
<zajec5@gmail.com> napisa?:
> W dniu 22 pa?dziernika 2010 13:23 u?ytkownik Rafa? Mi?ecki
> <zajec5@gmail.com> napisa?:
>> I've problem with initializing N radio (2055) on my Broadcom card.
>>
>> In case of my card simple workaround [1] for radio initialization is
>> needed. If I do not use workaround radio simply does not start. I
>> dumped MMIO operations of "wl" and it uses workaround for my card as
>> well.
>>
>> The problem is that workaround condition is SPROM-based. It looks like this:
>> if (sprom->revision < 4)
>> ? ? ? ?workaround = (some_specific_card);
>> else
>> ? ? ? ?workaround = ((sprom->boardflags_hi & B43_BFH_NOPA) == 0);
>>
>> So now goes the tricky part. My SSB has following SPROM:
>> [ 6208.080097] ssb: SPROM offset is 0x1000
>> [ 6208.089815] ssb: SPROM revision 5 detected.
>>
>> However in drivers/ssb/pci.c there are some translations, including
>> one for my card. My SPROM revision gets translated to 4. The result
>> is:
>> sprom->revision: 4
>> sprom->boardflags_hi: 0x1
>>
>> With that revision and boardflags workaround is not used and my radio
>> does not init. There are two possibilities:
>> 1) Specs are wrong
>> 2) We do SPROM translation incorrectly
>>
>> Any hints about that?
>>
>>
>> [1] http://bcm-v4.sipsolutions.net/802.11/Radio/2055/Init#Post_Init
>
> Ahhh, I should check for boardflags2! Expect patches soon ;)

Larry: could you check this and fix specs if I am right?

The way I understand this is following:
1) Workaround registers are:
a) 0x77: Core 1 RX Baseband Regulator
b) 0xa6: Core 2 RX Baseband Regulator
that really looks like regulatory-related
2) 0x00010000 BFL_NOPA has no PA
doesn't look like regulatory related
3) 0x00000001 BFL2_RXBB_INT_REG_DI external RX BB regulator present
looks like sth-related, so I guess we need to check for boardflags2

-- 
Rafa?

      reply	other threads:[~2010-10-22 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 11:23 b43/SSB: SPROM revision problem Rafał Miłecki
2010-10-22 12:41 ` Rafał Miłecki
2010-10-22 12:45   ` Rafał Miłecki [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='AANLkTinwXMcP3F=Py4S2sjJVpiRsXpVndXP-W55EAsBT@mail.gmail.com' \
    --to=zajec5@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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).