From: Oleksij Rempel <linux@rempel-privat.de>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
USB list <linux-usb@vger.kernel.org>,
Seth Forshee <seth.forshee@canonical.com>,
ath9k_htc_fw <ath9k_htc_fw@lists.infradead.org>
Subject: Re: FUSB200 xhci issue
Date: Sun, 28 Jul 2013 14:12:39 +0200 [thread overview]
Message-ID: <51F50AB7.3030204@rempel-privat.de> (raw)
In-Reply-To: <201307281338.39157.chunkeey@googlemail.com>
Am 28.07.2013 13:38, schrieb Christian Lamparter:
>>>
>>> Anyway, I tried the -next branch.
>>>
>>> commit dbbb809d592dde0b3c9ecb97b3b387ff8e40e799
>>> Author: Oleksij Rempel <linux@rempel-privat.de>
>>> Date: Wed Jul 24 10:26:18 2013 +0200
>>>
>>> k2_fw_usb_api: workaround for EP4 bug.
>>>
>>> but still, the device won't show up after autosuspend.
>>
>> Hm... firmware probably didn't rebooted before suspend. Did interface
>> was up, before autosuspend? If no, you need latest wireles-testing -
>> there are patches to handle this issue. Or just make "ifconfig wlan1 up"
>> before rmmod.
> Oh, I it was on the latest wireless-testing. (And the "ath9k_htc" module
> had the patch "ath9k_htc: reboot firmwware if it was loaded").
>
> Furthermore, I did the same test with one of the ehci-only ports
> and it worked. Both, devices (one had a AR7015, the other a AR9271)
> came back after autosuspend there.
Grrr... so it brings us back to xhci issue. Even EP4 workaround wont
work here :( Suddenly i have no more ideas.
Sarah, it's your turn now.
--
Regards,
Oleksij
next prev parent reply other threads:[~2013-07-28 12:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51ED4E12.8030006@rempel-privat.de>
2013-07-22 19:54 ` FUSB200 xhci issue Christian Lamparter
2013-07-22 20:47 ` Oleksij Rempel
2013-07-22 21:23 ` Christian Lamparter
2013-07-23 4:59 ` Oleksij Rempel
2013-07-23 18:26 ` Christian Lamparter
2013-07-24 10:37 ` Oleksij Rempel
2013-07-27 21:59 ` Christian Lamparter
2013-07-28 5:50 ` Oleksij Rempel
2013-07-28 11:38 ` Christian Lamparter
2013-07-28 12:12 ` Oleksij Rempel [this message]
2013-07-28 14:28 ` Oleksij Rempel
2013-07-28 20:41 ` Christian Lamparter
2013-07-31 6:52 ` Oleksij Rempel
2013-08-08 15:35 ` Oleksij Rempel
2013-08-08 19:09 ` Christian Lamparter
2013-08-08 20:19 ` Alan Stern
2013-08-08 22:06 ` Christian Lamparter
2013-08-09 2:52 ` Sujith Manoharan
2013-08-09 14:32 ` ath9k_htc firmware problem [was: Re: FUSB200 xhci issue] Alan Stern
2013-08-09 14:13 ` FUSB200 xhci issue Alan Stern
2013-08-09 14:34 ` Oleksij Rempel
2013-08-09 14:52 ` Alan Stern
2013-08-09 15:51 ` Oleksij Rempel
2013-08-09 17:16 ` Alan Stern
2013-08-09 18:53 ` Oleksij Rempel
2013-08-09 19:32 ` Alan Stern
2013-08-10 6:19 ` Oleksij Rempel
2013-08-10 11:57 ` Alan Stern
2013-08-12 7:58 ` 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=51F50AB7.3030204@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k_htc_fw@lists.infradead.org \
--cc=chunkeey@googlemail.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=seth.forshee@canonical.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.