From: "Rafał Miłecki" <zajec5@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Michael Buesch <mb@bu3sch.de>,
John Linville <linville@tuxdriver.com>,
wireless <linux-wireless@vger.kernel.org>,
b43-dev@lists.infradead.org
Subject: Changes in specs
Date: Wed, 31 Mar 2010 19:11:28 +0300 [thread overview]
Message-ID: <q2mb170af451003310911z830c4009o1aeb123b830cdd80@mail.gmail.com> (raw)
In-Reply-To: <4BB366C2.8010605@lwfinger.net>
2010/3/31 Larry Finger <Larry.Finger@lwfinger.net>:
> John Linville ran an MMIO dump on his Netbook while loading the wl
> driver. From the output, it was clear that his device does indeed have
> an SPROM, but it is in a different location than previous devices we
> have encountered. With this information, it was not difficult to find
> the test for this situation in the Broadcom code. The revised specs for
> this condition are in the first paragraph of
> http://bcm-v4.sipsolutions.net/SPROM. In a nutshell, the SPROM is at
> offset 0x1000 for chipcommon revisions < 31, and@0x0800 for revisions
>>= 31.
>
> I have also discovered what was wrong with the specs that described what
> devices do not have an SPROM. The previous version only covers those
> devices that are on a PCMCIA bus. The new version of those specs are at
> http://bcm-v4.sipsolutions.net/802.11/IsSpromAvailable. As might be
> expected, the chipcommon revision is again important for PCI devices.
I've is_sprom_available updated.
Will hack on SPROM today.
--
Rafa?
prev parent reply other threads:[~2010-03-31 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 15:14 Changes in specs Larry Finger
2010-03-31 16:11 ` 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=q2mb170af451003310911z830c4009o1aeb123b830cdd80@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=linville@tuxdriver.com \
--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).