Hi,
John Youn writes:
> I haven't checked, but Thinh looked and couldn't find anything
> relating to the macOS issue. Which is why we want more information
> about the problem.
>
> I can take a look at it too later today when I get a chance.
>
On 6/21/2017 3:38 AM, Felipe Balbi wrote:
>
> Hi,
>
> John Youn writes:
>
>
>
I haven't checked, but Thinh looked and couldn't find anything
relating to the macOS issue. Which is why we want more information
about the problem.
I can take a look at
On 6/13/2017 3:31 PM, Paul Zimmerman wrote:
> On Tue, 13 Jun 2017 21:57:42 +, John Youn wrote:
>
>> On 6/13/2017 2:39 PM, Paul Zimmerman wrote:
>>> On Tue, 13 Jun 2017 18:33:09 +, John Youn
>>> wrote:
>>>
On 6/13/2017 12:32 AM, Felipe
On Tue, 13 Jun 2017 21:57:42 +, John Youn wrote:
> On 6/13/2017 2:39 PM, Paul Zimmerman wrote:
> > On Tue, 13 Jun 2017 18:33:09 +, John Youn
> > wrote:
> >
> >> On 6/13/2017 12:32 AM, Felipe Balbi wrote:
> >>>
> >>> Hi,
> >>>
> >>> Thinh
On 6/13/2017 2:39 PM, Paul Zimmerman wrote:
> On Tue, 13 Jun 2017 18:33:09 +, John Youn wrote:
>
>> On 6/13/2017 12:32 AM, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Thinh Nguyen writes:
>> this could be, I don't remember if I
On Tue, 13 Jun 2017 18:33:09 +, John Youn wrote:
> On 6/13/2017 12:32 AM, Felipe Balbi wrote:
> >
> > Hi,
> >
> > Thinh Nguyen writes:
> this could be, I don't remember if I checked this or not :-)
>
>
On 6/13/2017 12:32 AM, Felipe Balbi wrote:
>
> Hi,
>
> Thinh Nguyen writes:
this could be, I don't remember if I checked this or not :-)
Really, the best way here, IMHO, would be to re-verify what's
going on
Hi,
On 6/13/2017 12:32 AM, Felipe Balbi wrote:
> Thinh Nguyen writes:
this could be, I don't remember if I checked this or not :-)
Really, the best way here, IMHO, would be to re-verify what's
going on
Hi,
Thinh Nguyen writes:
>>> this could be, I don't remember if I checked this or not :-)
>>>
>>> Really, the best way here, IMHO, would be to re-verify what's going
>>> on
>>> with macOS and revert my orignal patch since it's,
Hi Felipe,
On 6/6/2017 11:52 AM, Thinh Nguyen wrote:
> On 6/4/2017 11:08 PM, Felipe Balbi wrote:
>> Paul Zimmerman writes:
>>> Forgot to CC linux-usb, doing that now
>>>
>>> On Fri, 2 Jun 2017 16:27:56 -0700, Paul Zimmerman
>>> wrote:
>>>
Felipe
Hi Felipe,
On 6/4/2017 11:08 PM, Felipe Balbi wrote:
> Paul Zimmerman writes:
>> Forgot to CC linux-usb, doing that now
>>
>> On Fri, 2 Jun 2017 16:27:56 -0700, Paul Zimmerman wrote:
>>
>>> Felipe Balbi writes:
Thinh Nguyen
Hi,
Paul Zimmerman writes:
> Forgot to CC linux-usb, doing that now
>
> On Fri, 2 Jun 2017 16:27:56 -0700, Paul Zimmerman wrote:
>
>> Felipe Balbi writes:
>> > Thinh Nguyen writes:
>> >> this could be, I
Forgot to CC linux-usb, doing that now
On Fri, 2 Jun 2017 16:27:56 -0700, Paul Zimmerman wrote:
> Felipe Balbi writes:
> > Thinh Nguyen writes:
> >> this could be, I don't remember if I checked this or not :-)
> >>
>
Hi,
Thinh Nguyen writes:
> this could be, I don't remember if I checked this or not :-)
>
> Really, the best way here, IMHO, would be to re-verify what's going on
> with macOS and revert my orignal patch since it's, rather clearly,
> wrong.
>
Hi Felipe,
On 5/11/2017 6:12 PM, Thinh Nguyen wrote:
> On 4/11/2017 11:03 PM, Felipe Balbi wrote:
>> Thinh Nguyen writes:
>> Felipe Balbi writes:
>>> Thinh Nguyen writes:
This patch fixes a commit that
Hi Felipe,
On 4/11/2017 11:03 PM, Felipe Balbi wrote:
>
> Hi,
>
> Thinh Nguyen writes:
> Felipe Balbi writes:
>> Thinh Nguyen writes:
>>> This patch fixes a commit that causes a hang from device waiting for
Hi,
Thinh Nguyen writes:
Felipe Balbi writes:
> Thinh Nguyen writes:
>> This patch fixes a commit that causes a hang from device waiting for
>> data with the wrong sequence number. The commit ffb80fc672c3
On 4/11/2017 12:36 AM, Felipe Balbi wrote:
Hi,
Thinh Nguyen writes:
Felipe Balbi writes:
Thinh Nguyen writes:
This patch fixes a commit that causes a hang from device waiting for
data with the wrong sequence number.
Hi,
Thinh Nguyen writes:
>> Felipe Balbi writes:
>>> Thinh Nguyen writes:
This patch fixes a commit that causes a hang from device waiting for
data with the wrong sequence number. The commit ffb80fc672c3 ("usb:
Hi Felipe,
On 4/10/2017 12:04 AM, Felipe Balbi wrote:
Hi again,
Felipe Balbi writes:
Thinh Nguyen writes:
This patch fixes a commit that causes a hang from device waiting for
data with the wrong sequence number. The commit ffb80fc672c3 ("usb:
Hi again,
Felipe Balbi writes:
> Thinh Nguyen writes:
>> This patch fixes a commit that causes a hang from device waiting for
>> data with the wrong sequence number. The commit ffb80fc672c3 ("usb:
>> dwc3: gadget: skip Set/Clear Halt when invalid")
Hi,
Thinh Nguyen writes:
> This patch fixes a commit that causes a hang from device waiting for
> data with the wrong sequence number. The commit ffb80fc672c3 ("usb:
> dwc3: gadget: skip Set/Clear Halt when invalid") adds a check to return
> early depending on
This patch fixes a commit that causes a hang from device waiting for
data with the wrong sequence number. The commit ffb80fc672c3 ("usb:
dwc3: gadget: skip Set/Clear Halt when invalid") adds a check to return
early depending on DWC3_EP_STALL is set or not, prevent sending the ep
halt command to HW
23 matches
Mail list logo