Hi, Greg, Alan, All,
On 05/18/2013 06:17 PM, Greg KH wrote:
On Sat, May 18, 2013 at 12:14:08PM -0400, Alan Stern wrote:
On Sat, 18 May 2013, Hans de Goede wrote:
But the sysfs descriptors file will just packs the
rawdescriptors one behind the other, using
On Sat, 18 May 2013, Daniel Santos wrote:
Yes, my apologies, I didn't state that very clearly. I meant that I
submit a request URB to the in interrupt endpoint as well a response
URB to the out interrupt endpoint.This is where I'm currently submitting
these (for now just assume can_sleep
On Sun, 19 May 2013, Hans de Goede wrote:
Hi, Greg, Alan, All,
On 05/18/2013 06:17 PM, Greg KH wrote:
On Sat, May 18, 2013 at 12:14:08PM -0400, Alan Stern wrote:
On Sat, 18 May 2013, Hans de Goede wrote:
But the sysfs descriptors file will just packs the
rawdescriptors one behind the
Hi,
I've got hardware here to test with, so if there any changes to test, I'm
willing to support.
Meanwhile, might it be a good idea to make that check optional - i.e. add a
module parameter or something like this around it?
Regards,
M. Braun
On Thu, Apr 18, 2013 at 05:13:39PM +0200,
On Sun, May 19, 2013 at 11:20:59AM -0400, Alan Stern wrote:
By the way, Greg, at what point does it make sense to move things from
Documenation/ABI/testing to Documentation/ABI/stable? I get the
impression that nothing ever makes this jump.
One people start relying on the file, it should be
The value of offd comes off the instance-rcv_buf[] and we used it as
the offset into an array. The problem is that we check the upper bound
but not for negative values.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/usb/atm/cxacru.c b/drivers/usb/atm/cxacru.c
index
If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usbm=136547502011472w=2.
If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usbm=136547502011472w=2.
On Fri, May 17, 2013 at 10:27 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Fri, 17 May 2013, Peter Chen wrote:
I found out a couple more things about this.
If I do rmmod dwc3 first, and then do rmmod dwc3-pci, it doesn't
crash.
dwc3-pci will release dwc3 and its resources at
Hi Jean-Christophe,
On 5/17/2013 22:42, Jean-Christophe PLAGNIOL-VILLARD wrote:
Allow to compile the driver all the time if AT91 enabled.
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: linux-usb@vger.kernel.org
---
Hi Braun,
At that time I had an P4080DS board which had the same issue and had been fixed
with this patch.
I didn't test it on P1020 due to the absence of P1020. I think P1020 will need
a new patch besides this one.
Later Ramneek took this issue on P1020 for more investigation.
Hello Ramneek,
Hi Shengzhou/Braun,
We changed the controller init sequence to make this work. I'll submit the
patch upstream soon.
Regards,
Ramneek
-Original Message-
From: Liu Shengzhou-B36685
Sent: Monday, May 20, 2013 9:07 AM
To: Michael Braun; Mehresh Ramneek-B31383
Cc:
Hi,
When I used mass_storage as a gadget(use a linux-3.0.77 kernel),
After the following operations:
1.Turn my board into hibernation.
2.Plug the usb into host before resume.
3.Resume my board.
I saw some dump message like this, after some digging,
I think the other devices' retore time is too
Hi,
Another question from the bulk_out_complete() printout which is shown
below. The req-actual is 512 byte. The bh-bulk_out_intended_length
is 31. Is this a bug?
g_file_storage gadget: get_next_command
[start_transfer] 6f007442 7000
ept1 out queue len 0x200, buffer 0xc133
14 matches
Mail list logo
