From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>, John Linville <linville@tuxdriver.com>
Cc: wireless <linux-wireless@vger.kernel.org>, b43-dev@lists.infradead.org
Subject: Changes in specs
Date: Wed, 31 Mar 2010 10:14:10 -0500 [thread overview]
Message-ID: <4BB366C2.8010605@lwfinger.net> (raw)
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.
My workaround for missing SPROM data remains viable, and I plan to
resubmit it as soon as the revised detection routine is ready. Does that
sound reasonable, or should I wait until such a device is found?
Larry
WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>, John Linville <linville@tuxdriver.com>
Cc: wireless <linux-wireless@vger.kernel.org>, b43-dev@lists.infradead.org
Subject: Changes in specs
Date: Wed, 31 Mar 2010 10:14:10 -0500 [thread overview]
Message-ID: <4BB366C2.8010605@lwfinger.net> (raw)
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 at 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.
My workaround for missing SPROM data remains viable, and I plan to
resubmit it as soon as the revised detection routine is ready. Does that
sound reasonable, or should I wait until such a device is found?
Larry
next reply other threads:[~2010-03-31 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 15:14 Larry Finger [this message]
2010-03-31 15:14 ` Changes in specs Larry Finger
2010-03-31 16:11 ` Rafał Miłecki
2010-03-31 16:11 ` Rafał Miłecki
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=4BB366C2.8010605@lwfinger.net \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.