ler should return IRQ_NONE and let the UDC module IRQ handler to
deal with the IRQ event. And the IRQ handler can read the IRQ status to
determine the interrupt source.
Bryan Wu
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sujith
Sankar
Sent: Thursday, April
the device. The
speed of the USB transfer is very slow.
If comment out the mdelay(1), the enumeration will fail at very beginning
get_dev_descriptors operation as the same as disable debug message.
Could you please help me on this issue?
Thanks a lot
Best Regards
Bryan Wu
-Original Message-
F
Hi Ethan:
Thanks a lot.
Could you please give me some information about the illegal use of pointer
in detail during you development? I am digging into this bug for a long
time.
Best Regards,
Bryan Wu
-Original Message-
From: Ethan Du [mailto:[EMAIL PROTECTED]
Sent: Monday, April 17
message like printk.
So it is very difficult for me to find the problems.
Could you give me some idea about this?
My kernel is Linux 2.6.15 and my code structure is based on the sl811 and
isp116x.
Thanks a lot
Best Regards
Bryan Wu
---
This
g_file_storage gadget: get max LUN
> g_file_storage gadget: ep0-in, length 1:
> 0: 00
> g_file_storage gadget: ep0-setup, length 8:
> 0: 80 06 05 03 09 04 ff 00
> g_file_storage gadget: get string descriptor
> g_file_storage gadget: ep0-in, length 26:
> 0: 1a 03 4d 00
ce descriptor
> g_file_storage gadget: ep0-in, length 18:
> 0: 12 01 00 02 00 00 00 08 25 05 a5 a4 14 03 01 02
>10: 03 01
> g_file_storage gadget: ep0-setup, length 8:
> 0: 80 06 00 01 00 00 08 00
> g_file_storage gadget: get device descriptor
> g_file_storage gad
thread awakened.
> usb-storage: Bad target number (5:0)
> usb-storage: scsi cmd done, result=0x4
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand called
> usb-storage: *** thread awakened.
> usb-storage: Bad target number (6:0)
> usb-storage: scsi cmd done, result=0x4
>
