On Wed, 11 Sep 2013, Oleksij Rempel wrote:
> >> Same issue on two different intel controllers. I'll try some thing
> >> different for comparison.
> >
> > Don't try different hardware. Try submitting multiple URBs.
>
> Suddenly i can't submit multiple urbs, we have lots of read->write
> operatio
Am 07.09.2013 03:38, schrieb Alan Stern:
On Fri, 6 Sep 2013, Oleksij Rempel wrote:
Am 06.09.2013 23:09, schrieb Alan Stern:
On Fri, 6 Sep 2013, Oleksij Rempel wrote:
Hi Alan,
i need more help.
We have more test results now. Initial patch was probably fixing
fallowing issue - bad performanc
On Fri, 6 Sep 2013, Oleksij Rempel wrote:
> Am 06.09.2013 23:09, schrieb Alan Stern:
> > On Fri, 6 Sep 2013, Oleksij Rempel wrote:
> >
> >> Hi Alan,
> >>
> >> i need more help.
> >>
> >> We have more test results now. Initial patch was probably fixing
> >> fallowing issue - bad performance on EP4/
Am 06.09.2013 23:09, schrieb Alan Stern:
On Fri, 6 Sep 2013, Oleksij Rempel wrote:
Hi Alan,
i need more help.
We have more test results now. Initial patch was probably fixing
fallowing issue - bad performance on EP4/EP3 if Intr transfer is used.
It is reproducible only on EHCI, but not reprod
On Fri, 6 Sep 2013, Oleksij Rempel wrote:
> Hi Alan,
>
> i need more help.
>
> We have more test results now. Initial patch was probably fixing
> fallowing issue - bad performance on EP4/EP3 if Intr transfer is used.
> It is reproducible only on EHCI, but not reproducible on xHCI controller.
I
On Mon, 19 Aug 2013, Oleksij Rempel wrote:
> >> 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 ch
Am 10.08.2013 13:57, schrieb Alan Stern:
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 wi
Am 10.08.2013 13:57, schrieb Alan Stern:
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 wi
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 us
Am 09.08.2013 21:32, schrieb Alan Stern:
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
Is there any way to prevent the device from losing its firmware during
a USB reset or suspend?
For suspend - yes. It is possible to ignore suspend command or put the
SoC in low power mode - but is it probably n
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
> > Is there any way to prevent the device from losing its firmware during
> > a USB reset or suspend?
>
> For suspend - yes. It is possible to ignore suspend command or put the
> SoC in low power mode - but is it probably not so easy to bring it back.
Am 09.08.2013 19:16, schrieb Alan Stern:
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
Am 09.08.2013 16:52, schrieb Alan Stern:
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
What about a "get firmware version" sort of thing? There really should
be a way for the driver to tell whether the firmware h
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
> Am 09.08.2013 16:52, schrieb Alan Stern:
> > On Fri, 9 Aug 2013, Oleksij Rempel wrote:
> >
> >>> What about a "get firmware version" sort of thing? There really should
> >>> be a way for the driver to tell whether the firmware has already been
> >>> upd
Am 09.08.2013 16:52, schrieb Alan Stern:
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
What about a "get firmware version" sort of thing? There really should
be a way for the driver to tell whether the firmware has already been
updated.
I was not able to find good direct way to check firmware ve
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
> > What about a "get firmware version" sort of thing? There really should
> > be a way for the driver to tell whether the firmware has already been
> > updated.
>
> I was not able to find good direct way to check firmware version. If i
> would add some
Am 09.08.2013 16:13, schrieb Alan Stern:
On Fri, 9 Aug 2013, Christian Lamparter wrote:
After loading firmware, a reset generally is necessary. Some devices
will do it themselves; others require you to call usb_reset_device().
This makes things complicated. Because, as far as I remember,
usb
On Fri, 9 Aug 2013, Sujith Manoharan wrote:
> Christian Lamparter wrote:
> > So, if we call usb_reset_device there and the driver is unbound
> > and later rebound. the next ath9k_htc .probe will start again and
> > again and again not knowing that it is already initialized
> > (and we have a loop
On Fri, 9 Aug 2013, Christian Lamparter wrote:
> > After loading firmware, a reset generally is necessary. Some devices
> > will do it themselves; others require you to call usb_reset_device().
>
> This makes things complicated. Because, as far as I remember,
> usb_reset_device() will cause the
Christian Lamparter wrote:
> So, if we call usb_reset_device there and the driver is unbound
> and later rebound. the next ath9k_htc .probe will start again and
> again and again not knowing that it is already initialized
> (and we have a loop).
The HW/FW is buggy and this workaround is required:
On Thursday 08 August 2013 22:19:32 Alan Stern wrote:
> On Thu, 8 Aug 2013, Christian Lamparter wrote:
>
> > Anyway, I do have a question about something else too.
> >
> > in ath9k_htc's hif_usb:
> >
> > > struct usb_host_interface *alt = &hif_dev->interface->altsetting[0];
> > > struct usb_endp
On Thu, 8 Aug 2013, Christian Lamparter wrote:
> Anyway, I do have a question about something else too.
>
> in ath9k_htc's hif_usb:
>
> > struct usb_host_interface *alt = &hif_dev->interface->altsetting[0];
> > struct usb_endpoint_descriptor *endp;
> > ...
> > /* On downloading the firmware to t
On Thursday 08 August 2013 17:35:34 Oleksij Rempel wrote:
> Am 31.07.2013 08:52, schrieb Oleksij Rempel:
> > Am 28.07.2013 22:41, schrieb Christian Lamparter:
> >> On Sunday, July 28, 2013 04:28:25 PM Oleksij Rempel wrote:
> >>> Am 28.07.2013 14:12, schrieb Oleksij Rempel:
> Am 28.07.2013 13:3
Am 31.07.2013 08:52, schrieb Oleksij Rempel:
Am 28.07.2013 22:41, schrieb Christian Lamparter:
On Sunday, July 28, 2013 04:28:25 PM Oleksij Rempel wrote:
Am 28.07.2013 14:12, schrieb Oleksij Rempel:
Am 28.07.2013 13:38, schrieb Christian Lamparter:
before rmmod.
Oh, I it was on the lat
Am 28.07.2013 22:41, schrieb Christian Lamparter:
On Sunday, July 28, 2013 04:28:25 PM Oleksij Rempel wrote:
Am 28.07.2013 14:12, schrieb Oleksij Rempel:
Am 28.07.2013 13:38, schrieb Christian Lamparter:
Anyway, I tried the -next branch.
commit dbbb809d592dde0b3c9ecb97b3b387ff8e40e799
Autho
On Sunday, July 28, 2013 04:28:25 PM Oleksij Rempel wrote:
> Am 28.07.2013 14:12, schrieb Oleksij Rempel:
> > Am 28.07.2013 13:38, schrieb Christian Lamparter:
> >
>
> Anyway, I tried the -next branch.
>
> commit dbbb809d592dde0b3c9ecb97b3b387ff8e40e799
> Author: Oleksij Re
Am 28.07.2013 14:12, schrieb Oleksij Rempel:
Am 28.07.2013 13:38, schrieb Christian Lamparter:
Anyway, I tried the -next branch.
commit dbbb809d592dde0b3c9ecb97b3b387ff8e40e799
Author: Oleksij Rempel
Date: Wed Jul 24 10:26:18 2013 +0200
k2_fw_usb_api: workaround for EP4 bug.
but st
Am 28.07.2013 13:38, schrieb Christian Lamparter:
Anyway, I tried the -next branch.
commit dbbb809d592dde0b3c9ecb97b3b387ff8e40e799
Author: Oleksij Rempel
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 autosuspen
On Wednesday, July 24, 2013 12:37:55 PM Oleksij Rempel wrote:
> Am 23.07.2013 20:26, schrieb Christian Lamparter:
> > On Tuesday, July 23, 2013 06:59:46 AM Oleksij Rempel wrote:
> >> Am 22.07.2013 23:23, schrieb Christian Lamparter:
> >>> On Monday, July 22, 2013 10:47:41 PM Oleksij Rempel wrote:
>
Am 23.07.2013 20:26, schrieb Christian Lamparter:
On Tuesday, July 23, 2013 06:59:46 AM Oleksij Rempel wrote:
Am 22.07.2013 23:23, schrieb Christian Lamparter:
On Monday, July 22, 2013 10:47:41 PM Oleksij Rempel wrote:
Am 22.07.2013 21:54, schrieb Christian Lamparter:
Hello!
On Monday, July
On Tuesday, July 23, 2013 06:59:46 AM Oleksij Rempel wrote:
> Am 22.07.2013 23:23, schrieb Christian Lamparter:
> > On Monday, July 22, 2013 10:47:41 PM Oleksij Rempel wrote:
> >> Am 22.07.2013 21:54, schrieb Christian Lamparter:
> >>> Hello!
> >>>
> >>> On Monday, July 22, 2013 05:21:54 PM Oleksij
Am 22.07.2013 23:23, schrieb Christian Lamparter:
On Monday, July 22, 2013 10:47:41 PM Oleksij Rempel wrote:
Am 22.07.2013 21:54, schrieb Christian Lamparter:
Hello!
On Monday, July 22, 2013 05:21:54 PM Oleksij Rempel wrote:
i'm one of ath9k_htc devs. Currently i'm working on usb_suspend issu
31 matches
Mail list logo
