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
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
