From: "Rafał Miłecki" <zajec5@gmail.com>
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: b43-dev <b43-dev@lists.infradead.org>,
linux-wireless@vger.kernel.org, Michael Buesch <mb@bu3sch.de>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: ssb: how did we get special reject bit for SSB rev 2.3?
Date: Tue, 17 May 2011 13:45:31 +0200 [thread overview]
Message-ID: <BANLkTik59ohV42QYR3JqssbJjEzxnEGyOw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimoju5LSrKcRe67c41mCkPU0PUOjg@mail.gmail.com>
W dniu 17 maja 2011 13:32 użytkownik Jonas Gorski
<jonas.gorski@gmail.com> napisał:
> 2011/5/17 Rafał Miłecki <zajec5@gmail.com>:
>> 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?
>
> Broadcom public sources define it as follows:
> #define SBTML_REJ_MASK 0x0006 /* reject field */
> #define SBTML_REJ 0x0002 /* reject */
> #define SBTML_TMPREJ 0x0004 /* temporary reject,
> for error recovery */
>
>>
>> wl does never use this bit:
>
> It seems neither do the public ssb sources:
> # grep -r 'SBTML_TMPREJ' shared/ | wc -l
> 0
> #
Where did you check this? AFAIK wl has only linux_osl.c public
available and brcmsmac does not support SSB at all. Do you find any
references to SBTML_REJ in this "shared/*"?
--
Rafał
next prev parent reply other threads:[~2011-05-17 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 10:40 ssb: how did we get special reject bit for SSB rev 2.3? Rafał Miłecki
2011-05-17 11:20 ` 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 [this message]
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=BANLkTik59ohV42QYR3JqssbJjEzxnEGyOw@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=jonas.gorski@gmail.com \
--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).