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,
Gil Weber writes:
>> 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
Hi,
Gil Weber writes:
>> > 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 b0bac2581c1918cc4ab0aca01977ad69f0b
Hi,
Gil Weber writes:
>> 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
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.
Hi,
(please break your lines at 80-columns)
Gil Weber writes:
> I am experiencing some issues related USB Ethernet gadget with RNDIS
> on Kernel 4.4.
>
> On first connection everything seems OK, the device is correctly
> detected on my Windows 7 host.
>
> If I unplug/replug the USB cable, the d