From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc: Target is unresponsive
Date: Fri, 17 May 2013 12:48:53 +0200 [thread overview]
Message-ID: <51960B15.8030001@rempel-privat.de> (raw)
In-Reply-To: <20130517104047.GA14150@zenon.in.qult.net>
Am 17.05.2013 12:40, schrieb Ignacy Gawedzki:
> On Fri, May 17, 2013 at 12:30:34PM +0200, thus spake Ignacy Gawedzki:
>> On Fri, May 17, 2013 at 11:33:53AM +0200, thus spake Eugene Krasnikov:
>>> Did anybody tried to force the usb to go to suspend? If something like
>>> this "echo suspend | sudo tee /sys/bus/usb/devices/usb3/power/level"
>>> will help to reproduce this issue?
>>
>> This way of forcing suspend is apparently deprecated and doesn't work in my
>> case. I tried to set power/control to auto, but it has no apparent effect on
>> anything. :(
>
> Okay, I did manage to make it fail. In single-user mode (to prevent any
> daemon from interfering), I plugged the dongle, set power/control to "auto"
> and after a few seconds unloaded/reloaded the ath9k_htc module. This made the
> target unresponsive. If I do the same without setting power/control to "auto"
> (it is "on" by default), then unloading/reloading the module doesn't make the
> device unresponsive.
>
> BTW, Oleksij, just out of curiosity, how did you manage to solder those UART
> pins?
>
Here an example of soldered pins, it is ar7010 device. I attached here
jtag pins.
https://plus.google.com/u/0/102032716864870215256/posts/hZoEq8bo3zk
here is a workaround for this issue, please test it:
https://github.com/olerem/open-ath9k-htc-firmware/commits/suspend
--
Regards,
Oleksij
next prev parent reply other threads:[~2013-05-17 10:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 13:42 [ath9k-devel] ath9k_htc: Target is unresponsive Ignacy Gawedzki
2013-05-15 14:43 ` Eugene Krasnikov
2013-05-15 14:50 ` Kalle Valo
2013-05-15 16:11 ` Eugene Krasnikov
2013-05-15 16:34 ` Ignacy Gawedzki
2013-05-16 13:27 ` Oleksij Rempel
2013-05-16 17:20 ` Ignacy Gawedzki
2013-05-16 17:46 ` Oleksij Rempel
2013-05-16 18:50 ` Ignacy Gawedzki
2013-05-16 23:48 ` Ignacy Gawedzki
2013-05-16 23:45 ` Forest Bond
2013-05-17 6:00 ` Johannes Stezenbach
2013-05-17 8:07 ` Oleksij Rempel
2013-05-17 8:15 ` Ignacy Gawedzki
2013-05-17 8:31 ` Oleksij Rempel
2013-05-17 9:33 ` Eugene Krasnikov
2013-05-17 10:30 ` Ignacy Gawedzki
2013-05-17 10:40 ` Ignacy Gawedzki
2013-05-17 10:48 ` Oleksij Rempel [this message]
2013-05-17 11:22 ` Ignacy Gawedzki
2013-05-17 11:41 ` Ignacy Gawedzki
2013-05-17 12:00 ` Oleksij Rempel
2013-05-17 15:37 ` Adrian Chadd
2013-05-17 18:51 ` Oleksij Rempel
2013-05-18 10:59 ` Oleksij Rempel
-- strict thread matches above, loose matches on Subject: below --
2013-11-13 11:23 Rajeshwar Bandi
2013-11-13 14:39 ` Oleksij Rempel
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=51960B15.8030001@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k-devel@lists.ath9k.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