From: Fabio Rossi <rossi.f@inwind.it>
To: linux-wireless@vger.kernel.org
Subject: p54pci: problems during initialization
Date: Sat, 11 Jul 2009 20:06:44 +0200 [thread overview]
Message-ID: <200907112006.45731.rossi.f@inwind.it> (raw)
I have a PCMCIA card (3com 3CRWE154G72 v2) which has problems during the
device initialization phase. I'm using the current wireless.git and the
firmware included with the working Windows driver (extracted by fwextract).
Sometimes I'm able to get the card working but most of times it doesn't
complete the initialization. When it works dmesg reports:
pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
pci 0000:03:00.0: reg 10 32bit mmio: [0x000000-0x001fff]
pci 0000:03:00.0: supports D1 D2
pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:00.0: PME# disabled
p54pci 0000:03:00.0: enabling device (0000 -> 0002)
p54pci 0000:03:00.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
p54pci 0000:03:00.0: setting latency timer to 64
p54pci 0000:03:00.0: firmware: requesting isl3886pci
phy11: p54 detected a LM86 firmware
phy11: FW rev 2.5.2.0 - Softmac protocol 3.0
phy11: you are using an obsolete firmware. visit
http://wireless.kernel.org/en/users/Drivers/p54 and grab one for "kernel >=
2.6.28"!
phy11: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:no
phy11: hwaddr 00:0e:6a:xx:xx:xx, MAC:isl3890 RF:Frisbee
phy11: Selected rate control algorithm 'minstrel'
Registered led device: p54-phy11::assoc
Registered led device: p54-phy11::tx
Registered led device: p54-phy11::rx
Registered led device: p54-phy11::radio
p54pci 0000:03:00.0: is registered as 'phy11'
When it doesn't work I read:
pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
pci 0000:03:00.0: reg 10 32bit mmio: [0x000000-0x001fff]
pci 0000:03:00.0: supports D1 D2
pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:00.0: PME# disabled
p54pci 0000:03:00.0: enabling device (0000 -> 0002)
p54pci 0000:03:00.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
p54pci 0000:03:00.0: setting latency timer to 64
p54pci 0000:03:00.0: firmware: requesting isl3886pci
phy10: p54 detected a LM86 firmware
phy10: FW rev 2.5.2.0 - Softmac protocol 3.0
phy10: you are using an obsolete firmware. visit
http://wireless.kernel.org/en/users/Drivers/p54 and grab one for "kernel >=
2.6.28"!
phy10: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:no
phy10: device does not respond!
p54pci 0000:03:00.0: PCI INT A disabled
p54pci: probe of 0000:03:00.0 failed with error -16
pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0
It seems there is a problem inside the function p54_read_eeprom().
I have also tried with other firmwares available here
http://daemonizer.de/prism54/prism54-fw/
with the following results:
2.3.2.0.arm - same behaviour
2.4.2.0.arm - same behaviour
2.4.6.0.arm - same behaviour
2.4.8.0.arm - same behaviour
2.4.11.0.arm - same behaviour
2.4.12.0.arm - same behaviour
2.5.2.0.arm - same behaviour
2.5.3.0.arm - same behaviour
2.5.6.0.arm - same behaviour
2.7.0.0.arm - same behaviour
2.12.0.0.arm - same behaviour
2.13.1.0.arm - same behaviour
2.13.8.0.arm - cannot boot firmware, probe error -110
2.13.12.0.arm - cannot boot firmware, probe error -110
2.17.2.0.arm - cannot boot firmware, probe error -110
Any clue?
Fabio
reply other threads:[~2009-07-13 22:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200907112006.45731.rossi.f@inwind.it \
--to=rossi.f@inwind.it \
--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).