From: Alan Stern <stern@rowland.harvard.edu>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Seth Forshee <seth.forshee@canonical.com>,
ath9k_htc_fw <ath9k_htc_fw@lists.infradead.org>,
USB list <linux-usb@vger.kernel.org>,
<linux-wireless@vger.kernel.org>
Subject: Re: FUSB200 xhci issue
Date: Sat, 10 Aug 2013 07:57:13 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1308100755250.31571-100000@netrider.rowland.org> (raw)
In-Reply-To: <5205DB86.2050905@rempel-privat.de>
On Sat, 10 Aug 2013, Oleksij Rempel wrote:
> usb reset do not affect behaviour of firmware. At least after i remove
> all attempts to reboot FW from driver.
> If adapter will got reset signal, FW will be notified about it. Then FW
> will remove reset flag and will just continue to work. After usb reset,
> lsusb show correct, update information - EP3 and EP4 was updated from
> INT to BULK.
>
> I assume, no i need to add to the driver some kind of firmware check.
> What is the proper way to do it?
The simplest way is to put a new value for the device descriptor's
bcdDevice value in the firmware. Then all you have to do is check that
value.
Alan Stern
next prev parent reply other threads:[~2013-08-10 11:57 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
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 [this message]
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=Pine.LNX.4.44L0.1308100755250.31571-100000@netrider.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=ath9k_htc_fw@lists.infradead.org \
--cc=chunkeey@googlemail.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--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.