Hi Kyle,
I'm working with llandre for ISP1362 support on our board.
First of all thanks for your driver!
I've tested it with our PPC405EP-based board (after a few changes to support it,
of course), with the driver compiled into the kernel.
Here are some notes about it:
Using USB Storage Device (32MB Memory Stick):
1) device is recognized correctly when plugged in before booting or the first time it's plugged in
2) when in condition of point 1) the device is mounted correctly and works perfectly
3) regarding performance:
bash-2.05# time dd if=/dev/sda1 of=/tmp/dump-32MB.bin bs=1M count=32 31+1 records in 31+1 records out
real 1m38.491s user 0m0.020s sys 0m1.960s
which sounds very good to me! nice work! :-)
(BTW it is still a bit slower than the Philips one..)
4) when the device is plugged the first time (before or after boot is completed does not seem
to make differences) I receive this kind of messages:
hub.c: new USB device L-2, assigned address 2 Completion Code = 0x9 Completion Code = 0x9 usb_control/bulk_msg: timeout scsi0 : SCSI emulation for USB Mass Storage devices Completion Code = 0x9 Vendor: Model: Rev: Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 64000 512-byte hdwr sectors (33 MB) Completion Code = 0x9 sda: Write Protect is off Partition check: sda: sda1
It's seems there are some errors when trying to communicate with the device when it's plugged in, but, after that,
everything works fine..
5) after that, when plugged out and re-plugged in, I get this messages:
[unplugging...] ATL retry CC = 0x5, bytes = 0, OUT/IN:2 retry_count = 8 at fn = 443e usb.c: USB disconnect on device L-2 address 2 [re-plugging...] hub.c: new USB device L-2, assigned address 3 Completion Code = 0x9 Completion Code = 0x9
there are no prinkt() about SCSI device information but the device it's present in /proc/bus/usb/devices:
bash-2.05# cat /proc/bus/usb/devices Completion Code = 0x9 Completion Code = 0x9 T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= Completion Code = 0x9 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: ProdCompletion Code = 0x9 uct=USB OHCI Root Hub S: SerialNumber=c03c6400 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0c76 ProdID=0007 Rev= 1.00 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
If I try to mount the device I get this:
bash-2.05# mount -t vfat /dev/sda1 /mnt/hd/
Completion Code = 0x4
I/O error: dev 08:01, sector 0
FAT: unable to read boot sector
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
or too many mounted file systems
SCSI device sda: 64000 512-byte hdwr sectors (33 MB)
Completion Code = 0x9
sda: Write Protect is off
sda: sda1and the device is not mounted (but here there are the SCSI's printk()! :-).
With another mount command everything works fine...
BTW this kind of behaviour was present with the Philips driver too..
Using HID device (USB Keyboard & Mouse) I'm experiencing some problems :-(
1) when I plug the Keyboard I get a kernel panic:
hub.c: new USB device L-2, assigned address 2 Completion Code = 0x9 Completion Code = 0x9 usb_control/bulk_msg: timeout Completion Code = 0x9 input0: USB HID v10.01 Keyboard [USB Keyboard USB Keyboard] on usb1:2.0 INTL_INT!!!!!!!!! INTL retry CC = 0x3, bytes = 0, OUT/IN:2 retry_count = 9 at fn = f21 INTL_INT!!!!!!!!! INTL retry CC = 0x3, bytes = 0, OUT/IN:2 retry_count = 8 at fn = f29 usb_control/bulk_msg: timeout Oops: kernel access of bad area, sig: 11 NIP: C3482B58 XER: 00000000 LR: C3482B18 SP: C1B09CD0 REGS: c1b09c20 TRAP: 0800 Not tainted MSR: 00001030 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11 DEAR: 00000020, ESR: 00000000 TASK = c1b08000[149] 'syslogd' Last syscall: 118 last math 00000000 last altivec 00000000 PLB0: bear= 0x04001080 acr= 0x00000000 besr= 0x00000000 PLB0 to OPB: bear= 0x00040000 besr0= 0x00000000 besr1= 0x00000000
GPR00: 00000000 C1B09CD0 C1B08000 00000000 00009030 00000019 C016841C C02F9574 GPR08: 00000019 C1F4AC94 00000000 C00067E0 84004088 1001E938 10010000 10010000 GPR16: C3480000 00000000 00000002 C1F4AC00 00000001 00004000 C1F4ACB8 C1F4AC00 GPR24: 00086002 C3485BBC C02F9A20 C1EFF808 00000011 C3480000 C1EFF800 00000000 Call backtrace: C0166EDC C3481678 C3480BD8 C00058D0 C00059AC C000496C C0081DD4 C0081F1C C0078DDC C003B660 C000473C 10003080 10002BB0 100025BC 100023C4 10001B80 0FECAD14 00000000 Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing <0>Rebooting in 10 seconds..
2) while with the Mouse something seem to work:
hub.c: new USB device L-2, assigned address 2 Completion Code = 0x9 Completion Code = 0x9 input0: USB HID v10.01 Mouse [Logitech USB Mouse] on usb1:2.0
3) later, when I read from the /dev/input/eventX interface (with an input event reader tester application) I get:
./test-event /dev/input/event0 INTL_INT!!!!!!!!! Completion Code = 0x9 Event: time 1113298061.130077, type 2, code 0, value -1 INTL_INT!!!!!!!!! Completion Code = 0x9 Event: time 1113298061.141673, type 2, code 1, value -1 INTL_INT!!!!!!!!! Completion Code = 0x9 Event: time 1113298061.237981, type 2, code 1, value 1 INTL_INT!!!!!!!!! Completion Code = 0x9 Event: time 1113298061.247641, type 2, code 0, value 1 INTL_INT!!!!!!!!! Completion Code = 0x9 Event: time 1113298061.959628, type 2, code 1, value 1 INTL_INT!!!!!!!!! Completion Code = 0x9 Event: time 1113298061.971509, type 2, code 0, value 1 INTL_INT!!!!!!!!! Completion Code = 0x9 Event: time 1113298061.971521, type 2, code 1, value 1 Event: time 1113298061.981967, type 2, code 0, value 1 Event: time 1113298061.981979, type 2, code 1, value 1
After a while (a few seconds..) the device does not respond anymore.
If unplugged and plugged again the device is recognized but I do not see any event
on it..
I hope that this kind of test may help you someway.. of course I'm ready to do some other tests on it if you
have any idea where the problem can be! :-)
Best Regards,
Amon
DAVE Electronics System House - R&D Department web: http://www.dave-tech.it email: r&[EMAIL PROTECTED]
llandre, Here is the driver I have modified so far. We have it running on an MPC880 custom board. Currently, it does not use DMA. Using a Belkin USB Ethernet device, I am able to send TCP data at a rate of 250kB/s. Let me know how this works for you guys.
> We experienced similar problems. I mean that the host=20 > controller was not able to detect devices that were already=20 > plugged at boot. Let me check how we solved it ... I'll be back.
Our devices seem to work fine when they are plugged in upon boot. The problems occur when a device is removed and when it has data to be transferred in the buffers. The data cannot send, and no indication is received notifying the driver that the device has been disconnected. Also, a hub only works when it and its devices are connected before the driver is loaded. If the hub and/or its devices are connected after the driver is loaded, things just don't work. Please keep in mind we have only been using this driver as a module. We have not yet used it compiled into the kernel.
Thanks, Kyle
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
