From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH PING] ssb patches for SPROM location
Date: Mon, 26 Apr 2010 17:03:49 -0400 [thread overview]
Message-ID: <20100426210349.GA23289@tuxdriver.com> (raw)
In-Reply-To: <h2vb170af451004261249k43377e65n9d85f6dc7c377e67@mail.gmail.com>
On Mon, Apr 26, 2010 at 09:49:02PM +0200, Rafał Miłecki wrote:
> 2010/4/26 John W. Linville <linville@tuxdriver.com>:
> > P.S. With those patches, this box (soon to be Larry's) still uses
> > an sprom_offset value of 0x1000.
>
> Hm, so it looks like you device doesn't match our "if (version)"
> condition... It's just a blind guess, but maybe it would be worth to
> *force* other SPROM location on your machine? It seems quite proven
> that reading some incorrect registers (in this case incorrect SPROM
> location) can cause lock up. Of course it's just my guess, assuming
> you have other SPROM location, lock up is caused by reading wrong
> register and that Larry's condition in incorrect/not full. However if
> you're gonna to send whole machine to Larry, it sounds worthy to check
> this trick.
Well I thought I had done that before, but apparently not. I forced
sprom_offset to 0x0800 and ssb and b43 both load and act like they
are working. OTOH, b43 doesn't seem to be passing traffic but I may
just not have the right firmware...?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-04-26 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 6:20 [PATCH PING] ssb patches for SPROM location Rafał Miłecki
2010-04-16 13:37 ` John W. Linville
2010-04-16 15:51 ` Rafał Miłecki
2010-04-16 16:22 ` Larry Finger
2010-04-26 18:26 ` John W. Linville
2010-04-26 18:33 ` Rafał Miłecki
2010-04-26 19:04 ` Larry Finger
2010-04-26 19:09 ` John W. Linville
2010-04-26 19:49 ` Rafał Miłecki
2010-04-26 21:03 ` John W. Linville [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=20100426210349.GA23289@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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).