From: Larry Finger <Larry.Finger@lwfinger.net>
To: René_Bolldorf <xsecute@googlemail.com>
Cc: John Linville <linville@tuxdriver.com>,
LKML <linux-kernel@vger.kernel.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] No SPROM available!
Date: Mon, 29 Mar 2010 14:20:54 -0500 [thread overview]
Message-ID: <4BB0FD96.5020402@lwfinger.net> (raw)
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
Please also post the output of 'lspci -nnv | grep 14e4'.
Index: wireless-testing/drivers/ssb/sprom.c
===================================================================
--- wireless-testing.orig/drivers/ssb/sprom.c
+++ wireless-testing/drivers/ssb/sprom.c
@@ -182,6 +182,8 @@ bool ssb_is_sprom_available(struct ssb_b
if (bus->chipco.dev->id.revision < 11)
return true;
+ printk(KERN_INFO "ssb: chip_id 0x%x, status 0x%x\n", bus->chip_id,
+ bus->chipco.status);
switch (bus->chip_id) {
case 0x4312:
return SSB_CHIPCO_CHST_4312_SPROM_PRESENT(bus->chipco.status);
Larry
next reply other threads:[~2010-03-29 19:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 19:20 Larry Finger [this message]
2010-03-29 19:35 ` [BUG] No SPROM available! 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
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=4BB0FD96.5020402@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--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).