linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artur Skawina <art.08.09@gmail.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: p54usb and 2.13.24.0 Firmware fail to probe 1st generation 	(ISL3886 + net2280)
Date: Wed, 28 Jan 2009 03:53:30 +0100	[thread overview]
Message-ID: <497FC8AA.3030406@gmail.com> (raw)
In-Reply-To: <c4d76b3b0901271726v7c74e5bfpeb3bdb02e68c271d@mail.gmail.com>

Jason Andryuk wrote:
> On Tue, Jan 27, 2009 at 7:10 PM, Jason Andryuk <jandryuk@gmail.com> wrote:
>> With the below patch, -ETIMEDOUT is returned from usb_interrupt_msg in
>> addition to alen != sizeof(__le32)
>>
>> [   53.876103] usb 4-2: new high speed USB device using ehci_hcd and address 2
>> [   54.008792] usb 4-2: configuration #1 chosen from 1 choice
>> [   54.131230] usb 4-2: firmware: requesting isl3886usb
>> [   54.148759] phy1: p54 detected a LM86 firmware
>> [   54.148765] p54: rx_mtu reduced from 3240 to 2392
>> [   54.148770] phy1: FW rev 2.13.24.0 - Softmac protocol 5.9
>> [   54.148775] phy1: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES
>> [   56.316196] usb 4-2: (p54usb) err=-110, alen=0, size=4
>> [   56.316311] p54usb: probe of 4-2:1.0 failed with error -110
>> [   56.316356] usbcore: registered new interface driver p54usb

> Increasing the timeout to 9000 still results in -ETIMEDOUT.  Could the
> firmware just be incompatible with the device?

i'm seeing the same w/ another 1st gen device (t-sinus 154data), so likely yes.

[from an older post]
> Tried the newer fw, but it does not seem to like my hw:
> 
> usb 1-1.1: new full speed USB device using uhci_hcd and address 6
> usb 1-1.1: New USB device found, idVendor=0846, idProduct=4200
> usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> usb 1-1.1: configuration #1 chosen from 1 choice
> usb 1-1.1: firmware: requesting isl3886usb
> phy1: p54 detected a LM86 firmware
> p54: rx_mtu reduced from 3240 to 2392
> phy1: FW rev 2.13.24.0 - Softmac protocol 5.9
> phy1: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES
> p54usb: probe of 1-1.1:1.0 failed with error -110
> 
> Last one working is:
> 
> usb 1-1.1: new full speed USB device using uhci_hcd and address 5
> usb 1-1.1: New USB device found, idVendor=0846, idProduct=4200
> usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> usb 1-1.1: configuration #1 chosen from 1 choice
> usb 1-1.1: firmware: requesting isl3886usb
> phy0: p54 detected a LM86 firmware
> p54: rx_mtu reduced from 3240 to 2392
> phy0: FW rev 2.13.1.0 - Softmac protocol 5.5
> phy0: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES
> phy0: hwaddr 00:30:12:34:45:67, MAC:isl3886 RF:Frisbee
> wmaster0 (p54usb): not using net_device_ops yet
> phy0: Selected rate control algorithm 'minstrel'
> wlan0 (p54usb): not using net_device_ops yet
> mon.ap0 (p54usb): not using net_device_ops yet

artur


      reply	other threads:[~2009-01-28  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27  3:42 p54usb and 2.13.24.0 Firmware fail to probe 1st generation (ISL3886 + net2280) Jason Andryuk
2009-01-27  3:44 ` Jason Andryuk
2009-01-28  0:10   ` Jason Andryuk
2009-01-28  1:26     ` Jason Andryuk
2009-01-28  2:53       ` Artur Skawina [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=497FC8AA.3030406@gmail.com \
    --to=art.08.09@gmail.com \
    --cc=jandryuk@gmail.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).