From: Richard Farina <sidhayn@gmail.com>
To: Sujith <m.sujith@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: ath9k_htc oddity
Date: Mon, 11 Apr 2011 12:04:57 -0400 [thread overview]
Message-ID: <4DA326A9.9060904@gmail.com> (raw)
In-Reply-To: <19875.7684.859710.807182@gargle.gargle.HOWL>
On 04/11/11 11:28, Sujith wrote:
> Richard Farina wrote:
>> The following commit causes extreme sadness:
>> [ 4094.241243] usb 2-5: new high speed USB device using ehci_hcd and
>> address 3
>> [ 4095.550452] usb 2-5: ath9k_htc: Transferred FW: ar9271.fw, size: 51312
>> [ 4095.816072] ath9k_htc 2-5:1.0: ath9k_htc: HTC initialized with 33 credits
>> [ 4159.812888] usb 2-5: USB disconnect, address 3
>> [ 4159.929317] ath: Couldn't reset chip
>> [ 4159.929321] ath: Unable to initialize hardware; initialization status: -5
>> [ 4159.929323] ath: Unable to initialize hardware; initialization status: -5
>> [ 4159.929340] Failed to initialize the device
>> [ 4160.012603] ath9k_htc: probe of 2-5:1.0 failed with error -22
>> [ 4160.012771] usbcore: registered new interface driver ath9k_htc
>> [ 4163.595059] usb 2-5: new high speed USB device using ehci_hcd and
>> address 4
>> [ 4164.018920] usb 2-5: ath9k_htc: Transferred FW: ar9271.fw, size: 51312
>> [ 4164.284420] ath9k_htc 2-5:1.0: ath9k_htc: HTC initialized with 33 credits
>>
>> I'm guessing because I need the mentioned firmware update? Where can I
>> get it? Or better yet can you (this is almost laughable considering the
>> ralink thread right now) get it into linux-firmware? Or is the needed
>> firmware update an unstable thing?
> The new FW has to be formally/officially tested before it is merged into
> linux-firmware.
>
>> Either way I can wait on the firmware-version fix but where can I find
>> the patch that shows fixes the "driver: usb" issue? Your obviously shows
>> properly :-)
> http://linuxwireless.org/en/users/Drivers/ath9k_htc
Sorry for being a bit dim on this but which part of this exactly fixes
the ethtool driver function? I'm guessing it is in the patchset and the
firmware is only required if I want to detect the firmware version? Or
do I really need experimental firmware to make it detect the driver
properly?
Also, when you say experimental do you mean it's all pretty experimental
or just the AP stuff is? I'm guessing the firmware is based on the
current firmware so the station mode et al should be (approximately) as
stable at the released firmware and only the AP parts are experimental.
Thanks,
Rick Farina
> Sujith
>
next prev parent reply other threads:[~2011-04-11 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 3:03 ath9k_htc oddity Richard Farina
2011-04-09 5:44 ` Sujith
2011-04-11 14:36 ` Richard Farina
2011-04-11 15:28 ` Sujith
2011-04-11 15:29 ` Sujith
2011-04-11 16:04 ` Richard Farina [this message]
2011-04-11 16:14 ` Sujith
2011-04-11 16:59 ` Richard Farina
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=4DA326A9.9060904@gmail.com \
--to=sidhayn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=m.sujith@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).