ath9k_htc: Firmware - htc_9271.fw download failed

Oleksij Rempel linux at rempel-privat.de
Wed Jul 10 01:05:52 EDT 2013


Hi Bo,


Am 10.07.2013 04:24, schrieb Bo Shi:
> Hi Oleksij,
>      The issue has gone after patch this. thank you very very much.

Great! Thank you for testing.
Please write some feedback on github:
https://github.com/qca/open-ath9k-htc-firmware/issues/1
or to the mailing list

> |--- a/drivers/net/wireless/ath/ath9k/htc_drv_init.c
> +++ b/drivers/net/wireless/ath/ath9k/htc_drv_init.c
> @@ -895,6 +895,7 @@ static int ath9k_init_device(struct ath9k_htc_priv *priv,
>          ath9k_init_leds(priv);
>          ath9k_start_rfkill_poll(priv);
>
> +       ath9k_hw_disable(priv->ah);
>          return 0;
>
>   err_world:|
>
>
>
> On Tue, Jul 9, 2013 at 5:26 PM, Oleksij Rempel <linux at rempel-privat.de
> <mailto:linux at rempel-privat.de>> wrote:
>
>     Hi Bo,
>
>     Am 09.07.2013 06:21, schrieb Bo Shi:
>
>         Hi Oleksij,
>         I got the uart log from ar9271,
>
>
>     that's good news :)
>
>
>         first part is a fresh power on. second
>         part is from reboot system, could you please help to check the
>         issue?
>         Thanks you.
>         Bo
>
>         ==============================__==============================__======================
>         fresh system start up:
>         result: success
>         ==============================__==============================__======================
>
>
>     .....
>
>
>
>         ==============================__==============================__======================
>         do nothing to wlan0 interface after previous success
>         installment, just
>         reboot linux:
>         result:ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
>         ==============================__==============================__======================
>
>         !USB suspend
>
>            change clock to 22 and go to suspend now!ðð
>
>
>     this message is incomplete. I assume there was some hiccups on chip
>     reset.
>     ....
>
>
>
>         ==>[cUSB_REQ_COMP]: 0x%08x
>
>         VendorCmd: DownloadComplete!
>
>         5. usb only!!
>
>            A_WDT_INIT()
>
>            ==>warm start<==
>         ALLOCRAM start 0x50d7f4 size 106508
>         Enable Tx Stream mode
>         [+++Magpie_init]
>         [+++VBUF_init(100)]
>         [+++VBUF_init(100)]
>         <wlan_pci_probe>: Attaching the driver
>         <wlan_pci_probe>: Vendor id 0x168c Dev id 0x24
>         ath_pci_probe 24
>            ath_hal = 0x00510910
>
>         =>[dnQ] 0x0050f270
>         [=>[upQ] 0x0050f24c
>         [=>[hp dnQ] 0x0050f228
>         [=>[mp dnQ] 0x0050f204
>         [Tgt running
>
>
>     Usually my adapters was not able to boot if there was problem with
>     chip reset. Beside, only one case, where i get corrupt buffers and
>     chip was misconfigured after reboot and firmware upload.
>
>     May be it is that case. Please test this firmware:
>     https://github.com/olerem/__open-ath9k-htc-firmware/__commits/suspend_fix
>     <https://github.com/olerem/open-ath9k-htc-firmware/commits/suspend_fix>
>
>     with this kernel:
>     https://github.com/olerem/__linux-2.6/commits/github-wifi-__ath9k_htc-fw
>     <https://github.com/olerem/linux-2.6/commits/github-wifi-ath9k_htc-fw>
>     Or you can try to apply my patches on your kernel.
>
>     This firmware is not compatible with other kernel version. It wont
>     work without my kernel patches. And this firmware has an issue with
>     "ifconfig up"... so don't bring it up for now.
>
>
>
>         On Fri, Jul 5, 2013 at 10:50 PM, Bo Shi <cnshibo at gmail.com
>         <mailto:cnshibo at gmail.com>
>         <mailto:cnshibo at gmail.com <mailto:cnshibo at gmail.com>>> wrote:
>
>              Yes,they are the same. I will try uart log when I get another
>              module easy to open shield. Will let you know result ASAP.
>
>              在 2013年7月5日星期五,Oleksij Rempel 写道:
>
>                  Am 04.07.2013 03:05, schrieb Bo Shi:
>
>                      Sorry,
>                      'Target is unresponsive' with the latest patch
>         after reboot
>                      linux.
>
>                         I find if i do 'ifconfig wlan0 up'  or 'ifconfig
>         wlan0 up
>                        then
>                      ifconfig wlan0 down'  before reboot, everything
>         goes will
>                      after reboot.
>                      How 'ifconfig wlan0 up' command effect AR9217
>         hardware status?
>
>
>                      On Thu, Jul 4, 2013 at 2:48 AM, Oleksij Rempel
>                      <linux at rempel-privat.de <mailto:linux at rempel-privat.de>
>                      <mailto:linux at rempel-privat.de
>         <mailto:linux at rempel-privat.de>__>> wrote:
>
>                           Hi i can't reproduce your case, but i found
>         other case.
>                           It is enough to "rmmod ath9k_htc; sleep 1;
>         modprobe
>                      ath9k_htc;"
>                           some times more then one time.
>                           After some tesing i found that firmware can
>         freeze if
>                      after cpu
>                           reset we will continue configuration. So i
>         added some
>                      delay. Can you
>                           please test latest patch:
>         https://github.com/olerem/______open-ath9k-htc-firmware/______commits/suspend_fix
>         <https://github.com/olerem/____open-ath9k-htc-firmware/____commits/suspend_fix>
>
>         <https://github.com/olerem/____open-ath9k-htc-firmware/____commits/suspend_fix
>         <https://github.com/olerem/__open-ath9k-htc-firmware/__commits/suspend_fix>>
>
>
>
>         <https://github.com/olerem/____open-ath9k-htc-firmware/____commits/suspend_fix
>         <https://github.com/olerem/__open-ath9k-htc-firmware/__commits/suspend_fix>
>
>         <https://github.com/olerem/__open-ath9k-htc-firmware/__commits/suspend_fix
>         <https://github.com/olerem/open-ath9k-htc-firmware/commits/suspend_fix>>>
>
>
>                  Hi Bo,
>
>                  this bug seems to be same with this issue:
>         https://github.com/qca/open-____ath9k-htc-firmware/issues/1
>         <https://github.com/qca/open-__ath9k-htc-firmware/issues/1>
>
>
>         <https://github.com/qca/open-__ath9k-htc-firmware/issues/1
>         <https://github.com/qca/open-ath9k-htc-firmware/issues/1>>
>
>                  please fallow it
>
>                  --
>                  Regards,
>                  Oleksij
>
>
>
>
>     --
>     Regards,
>     Oleksij
>
>


-- 
Regards,
Oleksij



More information about the ath9k_htc_fw mailing list