From: "René Bolldorf" <xsecute@googlemail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] No SPROM available!
Date: Tue, 30 Mar 2010 01:21:16 +0200 [thread overview]
Message-ID: <4BB135EC.1070502@googlemail.com> (raw)
In-Reply-To: <4BB13147.9020002@lwfinger.net>
On 03/30/10 01:01, Larry Finger wrote:
> René and John,
>
> What output does this patch yield?
>
>
> Index: wireless-testing/drivers/ssb/sprom.c
> ===================================================================
> --- wireless-testing.orig/drivers/ssb/sprom.c
> +++ wireless-testing/drivers/ssb/sprom.c
> @@ -182,6 +182,11 @@ 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);
> + printk(KERN_INFO "ssb: cc rev 0x%x, cc capab 0x%x\n",
> + bus->chipco.dev->id.revision,
> + bus->chipco.capabilities);
> switch (bus->chip_id) {
> case 0x4312:
> return SSB_CHIPCO_CHST_4312_SPROM_PRESENT(bus->chipco.status);
>
>
ssb: chip_id 0x4312, status 0x12
ssb: cc rev 0x16, cc capab 0x18600000
And my system completely hangs after this... :(
next prev parent reply other threads:[~2010-03-29 23:21 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 [this message]
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=4BB135EC.1070502@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).