From: Mark Huijgen <mark.sf.net@huijgen.tk>
To: b43-dev@lists.infradead.org
Subject: [RFC/RFT] ssb: resolve alternate SPROM offset for 14e4:4315
Date: Thu, 06 May 2010 10:45:34 +0200 [thread overview]
Message-ID: <4BE281AE.7070901@huijgen.tk> (raw)
In-Reply-To: <4be24cdd.Yg6pH2Z4OwSotB+K%Larry.Finger@lwfinger.net>
On 05/06/2010 07:00 AM, Larry Finger wrote:
> This patch and the patch by Gabor entitled "[PATCH] ssb: Implement
> fast powerup delay calculation" are enough to allow the netbook from
> John to work with ssb/b43. As this patch tampers with the SPROM offset for
> 14e4:4315 devices, it should be tested by anyone with an LP PHY that works
> to ensure that it is not killed.
>
LP PHY device 14e4:4315 in my HP530 notebook still works after applying
the patch.
Messages from ssb after applying the patch:
[ 342.152271] b43-pci-bridge 0000:10:00.0: PCI INT A -> GSI 17 (level,
low) -> IRQ 17
[ 342.152286] b43-pci-bridge 0000:10:00.0: setting latency timer to 64
[ 342.172079] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor
0x4243)
[ 342.172090] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F,
vendor 0x4243)
[ 342.172100] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243)
[ 342.172110] ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243)
[ 342.192028] ssb: Found rev 1 PMU (capabilities 0x02A62F01)
[ 342.192034] ssb: SPROM offset is 0x1000
[ 342.208620] ssb: SPROM revision 8 detected.
[ 342.228069] ssb: Sonics Silicon Backplane found on PCI device
0000:10:00.0
Mark
next prev parent reply other threads:[~2010-05-06 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 5:00 [RFC/RFT] ssb: resolve alternate SPROM offset for 14e4:4315 Larry Finger
2010-05-06 8:45 ` Mark Huijgen [this message]
2010-05-06 9:53 ` Michael Buesch
2010-05-06 9:53 ` Michael Buesch
2010-05-06 10:01 ` Michael Buesch
2010-05-06 10:01 ` Michael Buesch
2010-05-06 13:11 ` Larry Finger
2010-05-06 13:11 ` Larry Finger
2010-05-06 22:44 ` Michael Buesch
2010-05-06 22:44 ` Michael Buesch
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=4BE281AE.7070901@huijgen.tk \
--to=mark.sf.net@huijgen.tk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.