linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 15:14:07 -0500	[thread overview]
Message-ID: <4BB10A0F.1030608@lwfinger.net> (raw)
In-Reply-To: <20100329194745.GH4984@tuxdriver.com>

On 03/29/2010 02:47 PM, John W. Linville wrote:
> On Mon, Mar 29, 2010 at 09:35:44PM +0200, René Bolldorf wrote:
>> On 03/29/10 21:20, Larry Finger wrote:
>>> Ren�,
>>>
>>> When you have a wireless problem, please post it to
>>> linux-wireless@vger.kernel.org. The Linux Kernel Mailing List may or may not be
>>> appropriate.
>>>
>>> To help in diagnosing your problem, please apply this patch and post the output
>>> line that it produces. On my system, it shows
>>>
>>> ssb: chip_id 0x4312, status 0x10
>>>
>> and on my: ssb: chip_id 0x4312, status 0x12
>>> Please also post the output of 'lspci -nnv | grep 14e4'.
>> Yep:
>> 01:00.0 Network controller [0280]: Broadcom Corporation BCM4312  
>> 802.11b/g [14e4:4315] (rev 01)
> 
> OK, I'm new to the thread -- what exactly is the issue?  Was your
> device working previously?

Yes. He originally posted only to LKML
(http://marc.info/?l=linux-kernel&m=126988911025280&w=2), where he posted

=========================
since commit fcb54b0bf7d3fe730c2b72e224bc616e358f24cb, my b43 (4312)
device doesn't work.

But the device have a sprom. Maybe the chip-status register check is wrong?

+/** Macros to determine SPROM presence based on Chip-Status register. */
+#define SSB_CHIPCO_CHST_4312_SPROM_PRESENT(status) \
+       ((status & SSB_CHIPCO_CHST_4325_SPROM_OTP_SEL) != \
+               SSB_CHIPCO_CHST_4325_OTP_SEL)
=======================================

I just happened to do one of my infrequent scans of LKML, and happened to see
it. In a follow-up, he proposes a patch that would fail on your system and leave
it locked up..

I rechecked the Broadcom driver, and stick by my specs that you used for your patch.

Could you please apply my little test patch and send me the contents of the
chipcommon status register in your netbook?

Thanks,

Larry

  parent reply	other threads:[~2010-03-29 20:14 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 [this message]
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

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=4BB10A0F.1030608@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).