From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Trouble using bcm4318 compact flash with b43 driver
Date: Tue, 01 Feb 2011 14:40:32 -0600 [thread overview]
Message-ID: <4D486FC0.3020507@lwfinger.net> (raw)
In-Reply-To: <20110201154135.00006f0b@unknown>
On 02/01/2011 08:41 AM, dylan cristiani wrote:
> i have some news: i went back to kernel version 2.6.26 and it worked
> so i moved forward kernel by kernel and it works till kernel 2.6.32;
> first kernel that shows up the problem is 2.6.33 and, at module loading
> time i can see for the first time, after loading firmware, the following
> debug info (don't know if it's helpful but same message happears in
> every non-working kernel from 2.6.33 to 2.6.37):
>
> "b43-phy0 warning: Invalid max-TX-power value in SPROM"
Between 2.6.32 and 2.6.33, there were only 6 patches that touched SSB. Two of
them (e33761e and 3ba6018) affected SPROM writing, one (37ace3d) was only for
PCMCIA, and one (ac2752c) only affected logging of a core scan. The two
remaining are 391ae22 that fixed an SDIO typo and 8b45499 that put host pointers
in a union should be the only ones that needed testing.
Those patches are attached. Try each of them in turn to 2.6.33 with a
'patch -p1 -R < patch_name' If it doesn't help, use the same command without the
"-R" to reapply. I'm guessing that 8b45499 is more likely to be the problem, and
I would try it first.
Larry
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch_391ae22
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20110201/340c8ec1/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch_8b45499
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20110201/340c8ec1/attachment-0001.ksh>
next prev parent reply other threads:[~2011-02-01 20:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 17:21 Trouble using bcm4318 compact flash with b43 driver dylan cristiani
2011-01-14 18:52 ` Larry Finger
2011-01-15 7:05 ` Dylan Cristiani
2011-01-15 16:38 ` Larry Finger
2011-01-17 10:06 ` dylan cristiani
2011-01-17 13:51 ` dylan cristiani
2011-01-18 10:58 ` dylan cristiani
2011-01-18 14:34 ` Larry Finger
2011-01-19 13:03 ` dylan cristiani
2011-01-21 15:51 ` Dylan Cristiani
2011-01-21 17:22 ` Larry Finger
2011-01-21 21:54 ` Dylan Cristiani
2011-01-21 22:13 ` Larry Finger
2011-01-22 10:48 ` Dylan Cristiani
2011-02-01 14:41 ` dylan cristiani
2011-02-01 20:40 ` Larry Finger [this message]
2011-02-02 9:11 ` dylan cristiani
2011-02-02 11:55 ` dylan cristiani
2011-02-02 15:30 ` dylan cristiani
2011-02-02 21:58 ` Larry Finger
2011-02-03 8:28 ` dylan cristiani
2011-02-02 22:40 ` Michael Büsch
2011-02-03 8:45 ` dylan cristiani
2011-02-03 10:29 ` Michael Büsch
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=4D486FC0.3020507@lwfinger.net \
--to=larry.finger@lwfinger.net \
--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;
as well as URLs for NNTP newsgroup(s).