From: "René Bolldorf" <xsecute@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.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 22:19:46 +0200 [thread overview]
Message-ID: <4BB10B62.9070408@googlemail.com> (raw)
In-Reply-To: <20100329194745.GH4984@tuxdriver.com>
On 03/29/10 21:47, 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?
>
> 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?
=============
diff --git a/include/linux/ssb/ssb_driver_chipcommon.h
b/include/linux/ssb/ssb_driver_chipcommon.h
index 2cdf249..1e0b9cd 100644
--- a/include/linux/ssb/ssb_driver_chipcommon.h
+++ b/include/linux/ssb/ssb_driver_chipcommon.h
@@ -386,6 +386,7 @@
/** Chip specific Chip-Status register contents. */
+#define SSB_CHIPCO_CHST_4312_SPROM_EXISTS 0x00000025
#define SSB_CHIPCO_CHST_4322_SPROM_EXISTS 0x00000040 /* SPROM present */
#define SSB_CHIPCO_CHST_4325_SPROM_OTP_SEL 0x00000003
#define SSB_CHIPCO_CHST_4325_DEFCIS_SEL 0 /* OTP is powered up, use
def. CIS, no SPROM */
@@ -403,7 +404,7 @@
/** 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)
+ SSB_CHIPCO_CHST_4312_SPROM_EXISTS)
#define SSB_CHIPCO_CHST_4322_SPROM_PRESENT(status) \
(status & SSB_CHIPCO_CHST_4322_SPROM_EXISTS)
#define SSB_CHIPCO_CHST_4325_SPROM_PRESENT(status) \
so my won't work then.
next prev parent reply other threads:[~2010-03-29 20:19 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 [this message]
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=4BB10B62.9070408@googlemail.com \
--to=xsecute@googlemail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).