From: "Rafał Miłecki" <email@example.com>
To: "Michael Büsch" <firstname.lastname@example.org>
Cc: email@example.com, Christoph Fritz <firstname.lastname@example.org>,
Larry Finger <Larry.Finger@lwfinger.net>,
Subject: Re: ssb: 184.108.40.206 -> 220.127.116.11 regression
Date: Sat, 7 Aug 2010 08:29:49 +0200 [thread overview]
Message-ID: <AANLkTikotSiDU1ZGetwB8=XJVZrn-HQYDHGm8KT1dVPF@mail.gmail.com> (raw)
2010/8/7 Michael Büsch <email@example.com>:
> The SPROM changes applied to SSB in 18.104.22.168 completely broke SPROM
> extraction. This leads to broken wireless for my BCM4306 card.
> All other BCM43xx and BCM44xx most likely are affected, too.
> Symptoms should be wrong MAC addresses and broken transmission (for 43xx).
> The patch changed the SPEX() macro and removed the offset subtraction,
> but did not remove the actual 0x1000 offset from the SPROM defines.
> This results in random memory poking rather than proper SPROM data
> I applied the following to my kernel to get it working again. However
> this is not a proper fix. I suggest that the -stable SSB patch
> is dropped and mainline patches being applied. They seem to
> be correct (However I did not test mainline, yet).
The original patch didn't simply drop subtraction of offset, it also
modified defines in .h:
It's Larry combined patch that you see in .34.2 and it indeed lacks
changes in defines. We already explained that situation, Greg will
revert it and apply correct patches instead.
prev parent reply other threads:[~2010-08-07 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 22:53 ssb: 22.214.171.124 -> 126.96.36.199 regression Michael Büsch
2010-08-06 23:56 ` [stable] " Greg KH
2010-08-07 10:44 ` Michael Büsch
2010-08-07 6:29 ` Rafał Miłecki [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).