From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev <b43-dev@lists.infradead.org>,
linux-wireless@vger.kernel.org, Michael Buesch <mb@bu3sch.de>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: ssb: how did we get special reject bit for SSB rev 2.3?
Date: Tue, 17 May 2011 12:40:10 +0200 [thread overview]
Message-ID: <BANLkTik2Sc9aWi_cHVvLJzGv3esey=wPag@mail.gmail.com> (raw)
I've just received 14e4:4312 card which is G-PHY BCM4311.
I've checked for SSB rev in MMIO dump:
read32 0xfaafcff8 -> 0x100422c5
0x100422c5 & (SSB_IDLOW_SSBREV == 0xF0000000) = 0x10000000
So this is SSB rev 2.3:
#define SSB_IDLOW_SSBREV_23 0x10000000 /* 2.3 */
Currently we are using different REJECT bit for SSB rev 2.3:
#define SSB_TMSLOW_REJECT 0x00000002 /* Reject (Standard Backplane) */
#define SSB_TMSLOW_REJECT_23 0x00000004 /* Reject (Backplane rev 2.3) */
Does anyone know where did we get this from?
wl does never use this bit:
$ grep "ssb_write32(0xf98)" wl.4312.txt | sort | uniq
ssb_write32(0xf98) <- 0x00000003
ssb_write32(0xf98) <- 0x00010000
ssb_write32(0xf98) <- 0x00010002
ssb_write32(0xf98) <- 0x00030003
ssb_write32(0xf98) <- 0x00040003
ssb_write32(0xf98) <- 0x00070000
ssb_write32(0xf98) <- 0x00070001
ssb_write32(0xf98) <- 0x00070003
ssb_write32(0xf98) <- 0x20010000
ssb_write32(0xf98) <- 0x20010002
ssb_write32(0xf98) <- 0x20040003
ssb_write32(0xf98) <- 0x20070000
ssb_write32(0xf98) <- 0x20070001
ssb_write32(0xf98) <- 0x20070003
--
Rafał
next reply other threads:[~2011-05-17 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 10:40 Rafał Miłecki [this message]
2011-05-17 11:20 ` ssb: how did we get special reject bit for SSB rev 2.3? Michael Büsch
2011-05-17 11:50 ` Rafał Miłecki
2011-05-17 13:14 ` Rafał Miłecki
2011-05-17 11:32 ` Jonas Gorski
2011-05-17 11:45 ` Rafał Miłecki
2011-05-17 12:17 ` Jonas Gorski
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='BANLkTik2Sc9aWi_cHVvLJzGv3esey=wPag@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).