From: "John W. Linville" <linville@tuxdriver.com>
To: "René Bolldorf" <xsecute@googlemail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] No SPROM available!
Date: Mon, 29 Mar 2010 16:30:05 -0400 [thread overview]
Message-ID: <20100329203005.GK4984@tuxdriver.com> (raw)
In-Reply-To: <4BB10B62.9070408@googlemail.com>
On Mon, Mar 29, 2010 at 10:19:46PM +0200, René Bolldorf wrote:
> On 03/29/10 21:47, John W. Linville wrote:
>> OK, I'm new to the thread -- what exactly is the issue? Was your
>> device working previously?
>>
>> John
>
> The problem is since commit fcb54b0bf7d3fe730c2b72e224bc616e358f24cb, my
> b43 (4312)
> device doesn't work because i get the message "No SPROM available" and
> then the device get's disabled.
>
> My colleague have the same problem. I have made a patch for that but it
> seems thats not work for all 4312 devices. I and my colleage have the
> same netbook for testing purposes so the patch work while we have the
> same chip status.
>
> The problem is I think: Larry had written his output is ssb: chip_id
> 0x4312, status 0x10, he have a different chip status.
> What to do? Any ideas?
Not really, no... :-(
Larry, any chance the definitions of those OTP_SEL bits are inverted
between 4325 and 4312?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-03-29 20:45 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
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 [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=20100329203005.GK4984@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--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).