Hello,
I have a device running on Atmel AT91 SAM9X5 processor with an USB modem
(Sagemcom Hilo 3G). Until now, it worked fine... Our firmware was based on
Kernel 3.12. USB Host driver is ehci-atmel.
We recently upgrade to a Kernel 4.9.
Now one of our customer is having issues with a couple of devi
Hello,
I have a device running on Atmel AT91 SAM9X5 processor with an USB modem
(Sagemcom Hilo 3G). Until now, it worked fine... Our firmware was based on
Kernel 3.12. USB Host driver is ehci-atmel.
We recently upgrade to a Kernel 4.9.
Now one of our customer is having issues with a couple of devi
Hi,
>> To make sure, I have also performed some additional tests. The problem
>> seems unrelated to the gadget being used: I have tried various
>> combinations (zero, ethernet, etc.), even setting up an ACM device
>> using configfs, and the result is the same: a host detects the device
>> for a br
Hi,
>UDC driver should NEVER do anything behind
>udc-core's back, so let's stop disabling endpoints
>we don't exactly own - rather we provide as
>resources for gadget drivers. This fixes the
>regression reported by Gil.
>
>Reported-by: Gil Weber
>Signed-of
Hi,
> > I finally bisect the kernel (I didn't known that command, thanks for the
> > tip)
> > and found that it doesn't work anymore from this commit :
> >
> > b0bac2581c1918cc4ab0aca01977ad69f0bc127a is the first bad commit
> > commit b0bac2581c1918cc4ab0aca01977ad69f0bc127a
> > Author: Robert B
Hi,
I finally bisect the kernel (I didn't known that command, thanks for the
tip)
and found that it doesn't work anymore from this commit :
b0bac2581c1918cc4ab0aca01977ad69f0bc127a is the first bad commit
commit b0bac2581c1918cc4ab0aca01977ad69f0bc127a
Author: R
Hi,
> interesting. Wonder what Windows is doing differently. Yeah, I guess the
> best way forward is to find which commit caused the regression and git
> bisect is the way to do that. Would be nice to see v3.13, v3.14,
> v3.15... are working or not. The idea is to find the smallest interval
> for
Hi,
> from your logs below, it seems like you're using atmel_usba_udc.c,
> right? That driver was merged during v3.17 merge window, how come it was
> working for you on v3.12 ?
>
> Can you try v3.17, when that driver was merged ?
It was already in previous versions as I used it in 3.12 and 3.5.
t;[ 280.011000] rndis_setup:525: g_ether gadget: rndis req21.00 v i
l24
<7>[ 280.011000] rndis_msg_parser:810: rndis_msg_parser: RNDIS_MSG_INIT
Does some body have an idea of what is going on? Is this a regression in the
latest version of the Kernel?
My configuration is and arm tar
