Hi,
On Wed, Dec 16, 2015 at 9:36 AM, Doug Anderson wrote:
> Hi,
>
> On Wed, Dec 16, 2015 at 7:35 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> John Youn writes:
>>> On 12/15/2015 3:49 PM, Heiko Stübner wrote:
Hi,
it seems the recent dwc2 additions to the testing/next branch [0] caused
Hi,
Doug Anderson writes:
it seems the recent dwc2 additions to the testing/next branch [0] caused
some interesting issue for me.
Setting is a regular 4.4-rc3/4 (only with some display-stuff added), and
the
testing/next branch merged in.
If I attach a sin
Hi,
On Wed, Dec 16, 2015 at 7:35 AM, Felipe Balbi wrote:
>
> Hi,
>
> John Youn writes:
>> On 12/15/2015 3:49 PM, Heiko Stübner wrote:
>>> Hi,
>>>
>>> it seems the recent dwc2 additions to the testing/next branch [0] caused
>>> some interesting issue for me.
>>>
>>> Setting is a regular 4.4-rc3/4
Hi,
John Youn writes:
> On 12/15/2015 3:49 PM, Heiko Stübner wrote:
>> Hi,
>>
>> it seems the recent dwc2 additions to the testing/next branch [0] caused
>> some interesting issue for me.
>>
>> Setting is a regular 4.4-rc3/4 (only with some display-stuff added), and the
>> testing/next branch
On 12/15/2015 3:49 PM, Heiko Stübner wrote:
> Hi,
>
> it seems the recent dwc2 additions to the testing/next branch [0] caused
> some interesting issue for me.
>
> Setting is a regular 4.4-rc3/4 (only with some display-stuff added), and the
> testing/next branch merged in.
>
> If I attach a sing
Hi,
it seems the recent dwc2 additions to the testing/next branch [0] caused
some interesting issue for me.
Setting is a regular 4.4-rc3/4 (only with some display-stuff added), and the
testing/next branch merged in.
If I attach a single usb device everything still works fine, but once it
is conn
