From: Paul TBBle Hampson <Paul.Hampson@Pobox.com>
To: linux-wireless@vger.kernel.org
Subject: Re: prism54pci fails to read eeprom on PowerPC, then bugs in pci code
Date: Sat, 17 Mar 2007 18:34:53 +1100 [thread overview]
Message-ID: <20070317073453.GD5954@keitarou> (raw)
In-Reply-To: <200703170244.54114.flamingice@sourmilk.net>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
On Sat, Mar 17, 2007 at 02:44:49AM -0400, Michael Wu wrote:
> On Saturday 17 March 2007 02:15, Paul TBBle Hampson wrote:
>> Is it worth dumping the purported eeprom to see if it's actually a valid
>> eeprom in a format unexpected by the code? (The card is very old now...)
> Actually, the code doesn't check (but it does report) if parsing fails so a
> corrupted eeprom can't be the reason for probe failure. I'll get that fixed
> next week..
> So anyway, your card isn't even returning the eeprom data. Only thing I can
> think of is fiddling with the mdelay in that (p54p_read_eeprom) function
> (there's only one). Try making it bigger. That mdelay solved problems with
> eeprom reading on module reload but it's very close to the minimum delay
> needed there.
mdelay of 500 and 5000 didn't seem to help.
Would the result of any of the P54P_READs help? Or do they not produce
anything useful at this stage?
--
-----------------------------------------------------------
Paul "TBBle" Hampson, B.Sc, LPI, MCSE
On-hiatus Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
Paul.Hampson@Pobox.Com
Of course Pacman didn't influence us as kids. If it did,
we'd be running around in darkened rooms, popping pills and
listening to repetitive music.
-- Kristian Wilson, Nintendo, Inc, 1989
License: http://creativecommons.org/licenses/by/2.1/au/
-----------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-17 7:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 3:46 prism54pci fails to read eeprom on PowerPC, then bugs in pci code Paul TBBle Hampson
2007-03-17 4:37 ` Michael Wu
2007-03-17 4:50 ` Pavel Roskin
2007-03-17 5:05 ` Michael Wu
2007-03-17 7:02 ` Pavel Roskin
2007-03-17 6:52 ` Paul TBBle Hampson
2007-03-17 7:20 ` mac80211 and IPv6 Duplicate Address Detection (Was: prism54pci fails to read eeprom on PowerPC, then bugs in pci code) Paul TBBle Hampson
2007-03-17 6:15 ` prism54pci fails to read eeprom on PowerPC, then bugs in pci code Paul TBBle Hampson
2007-03-17 6:44 ` Michael Wu
2007-03-17 7:34 ` Paul TBBle Hampson [this message]
2007-03-19 4:11 ` Luis R. Rodriguez
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=20070317073453.GD5954@keitarou \
--to=paul.hampson@pobox.com \
--cc=linux-wireless@vger.kernel.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).