From: "Michael Büsch" <mb@bu3sch.de>
To: b43-dev@lists.infradead.org
Subject: Interesting note on "Unsupported SPROM revision"
Date: Mon, 14 Feb 2011 21:29:55 +0100 [thread overview]
Message-ID: <1297715395.11070.5.camel@Nokia-N900> (raw)
In-Reply-To: <AANLkTinJDQDjhnzMBPubNkowxrXFDfOEz83HA1fHgEDU@mail.gmail.com> (sfid-20110214_072801_981891_D319F6EF)
> That resulted in:
> [? ? ? 6.681088] ssb: PCI-ID not in fallback list
> [? ? ? 6.681251] ssb: CHIPID not in nrcores fallback list
> [? ? ? 6.681433] ssb: Core 0 found: UNKNOWN (cc 0x8FF, rev 0x7F, vendor
> 0xFFFF) [? ? ? 6.689462] ssb: WARNING: Invalid SPROM CRC (corrupt SPROM)
> [? ? ? 6.689467] ssb: Unsupported SPROM? revision 255 detected. Will
> extract v1 [? ? ? 6.697123] ssb: Sonics Silicon Backplane found on PCI
>
> Just wanted to put it on ML in case someone will ever hit that issue.
>
all mmio reads return all-ones. That usually means your pci(e) does not work.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20110214/9d9230df/attachment.html>
prev parent reply other threads:[~2011-02-14 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 12:28 Interesting note on "Unsupported SPROM revision" Rafał Miłecki
2011-02-14 20:29 ` Michael Büsch [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=1297715395.11070.5.camel@Nokia-N900 \
--to=mb@bu3sch.de \
--cc=b43-dev@lists.infradead.org \
/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