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:59:37 -0400 [thread overview]
Message-ID: <4DA33379.5020708@gmail.com> (raw)
In-Reply-To: <19875.10497.371960.179673@gargle.gargle.HOWL>
On 04/11/11 12:14, Sujith wrote:
> Richard Farina wrote:
>> 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?
> The ethtool fix is part of the patchset (specifically patch no. 3),
> and the new FW is required if the patchset is used.
Patch number 3 seems to fix only the firmware version grabbing. Am I
misunderstanding the part or is the driver name grabbing fixed somewhere
else in a different place? In linus tree driver shows as "usb", Your
ethtool output showed driver properly as "ath9k_htc".
-Rick
>> 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.
> Yes, the new version is based on the current FW and the AP stuff is experimental.
> Station mode should ideally not have any problems, but since the firmware
> has had a fairly invasive cleanup, one can never know. :)
>
> Sujith
>
prev parent reply other threads:[~2011-04-11 16:59 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
2011-04-11 16:14 ` Sujith
2011-04-11 16:59 ` Richard Farina [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=4DA33379.5020708@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).