From: Larry Finger <Larry.Finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "René Bolldorf" <xsecute@googlemail.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] No SPROM available!
Date: Mon, 29 Mar 2010 16:28:46 -0500 [thread overview]
Message-ID: <4BB11B8E.1020506@lwfinger.net> (raw)
In-Reply-To: <20100329205558.GM4984@tuxdriver.com>
On 03/29/2010 03:55 PM, John W. Linville wrote:
> On Mon, Mar 29, 2010 at 04:48:22PM -0400, John W. Linville wrote:
>> On Mon, Mar 29, 2010 at 03:14:07PM -0500, Larry Finger wrote:
>>
>>> Could you please apply my little test patch and send me the contents of the
>>> chipcommon status register in your netbook?
>>
>> Mine looks like yours, "chip_id 0x4312, status 0x12"...
>
> I guess I misread the earlier messages -- mine looks like René's, not yours.
Bummer. To answer your previous message, the Broadcom driver is very clear that
0x2 set in the chipcommon status for a BCM4312 means no SPROM; however, René's
device contradicts that conclusion. There must be some other test that I have
missed.
René: For your information, this test was added because attempting to read the
SPROM in John's computer locks the processor - he has to power off. I did
reverse engineering on the Broadcom driver and found their workaround when no
SPROM is present. The patch in question matches their code, and allows John's
machine to continue. There is a second, pending patch that works with some udev
rules to create a virtual SPROM image and assign a unique MAC address. With this
patch applied, your machine would still work. The only change is that you would
be assigned a random MAC address.
I will likely need some additional test prints to see if I can find a test that
recognizes that René's machine has an SPROMs and that John's does not.
Larry
next prev parent reply other threads:[~2010-03-29 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 19:20 [BUG] No SPROM available! Larry Finger
2010-03-29 19:35 ` René Bolldorf
2010-03-29 19:47 ` John W. Linville
2010-03-29 20:04 ` John W. Linville
2010-03-29 20:14 ` Larry Finger
2010-03-29 20:48 ` John W. Linville
2010-03-29 20:55 ` John W. Linville
2010-03-29 21:28 ` Larry Finger [this message]
2010-03-29 21:53 ` René Bolldorf
2010-03-29 23:01 ` Larry Finger
2010-03-29 23:21 ` René Bolldorf
2010-03-29 23:43 ` Larry Finger
2010-03-29 23:45 ` René Bolldorf
2010-03-29 20:19 ` René Bolldorf
2010-03-29 20:30 ` John W. Linville
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=4BB11B8E.1020506@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=xsecute@googlemail.com \
/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).