[linux-usb-devel] USB Mouse
Hi All, I am emulating the USB mouse from a PPC based controller. ie PPC acts as a mouse. Currently, I am going through usbmouse.c. Is it enough to go through this file alone to send the X, Y co-ordinatinates to the host PC ? Or put it in a simpler way, how to send the mouse co-ordinates to the host PC from a target running on linux ? Thanks All, Jayaprakash. --- 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://productguide.itmanagersjournal.com/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] USB mouse on linux
Hi All, I use MPC 8270 based board and it has an USB 1.1 device port available in it. I want to make this device to act as a mouse. I need to have mouse movement, left click , right click and the middle click events. To give you a general picture : I want to emulate the USB mouse using the USB device port available on my board. What is the right file to tweak in ? I run Monta Vista 3.1 in my board. At present, it seems that I need to write the driver for this and Monta vista doesn't have a mouse driver. Any links that talks about the USB mouse on the device side would be great for me. Thanks, Jayaprakash. = The greatest glory is not in never falling, but in rising every time we fall. __ Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com --- 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://productguide.itmanagersjournal.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] PCI - USB 2.0 on 2.4
Hi All, I tried a PCI - USB 2.0 card (from D-Link, Ali based Chipset) on my PC which runs Redhat 9.0 (2.4 kernel). My linux detects the card and loads the driver. I tried my pen drive with it. It detects the drive and enumerates it. (It says the vendor ID, product ID etc.,) But when I tried to mount it, it fails. Is there anything I should do make my PCI - USB work on 2.4 kernel ? Thanks Regards, Jayaprakash. --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] PCI - USB 2.0 on 2.4
Thanks for the inputs Dave. I am insisting on 2.4 kernel was because I am going to use Montavista 3.1 which is 2.4 based. I will give a try on 2.4.29. I tested it on 2.4.20. Thanks Again, Jayaprakash On Fri, 21 Jan 2005 10:25:13 -0800, David Brownell [EMAIL PROTECTED] wrote: On Friday 21 January 2005 5:06 am, Jayaprakash Shanmugam wrote: Hi All, I tried a PCI - USB 2.0 card (from D-Link, Ali based Chipset) on my PC which runs Redhat 9.0 (2.4 kernel). My linux detects the card and loads the driver. I tried my pen drive with it. It detects the drive and enumerates it. (It says the vendor ID, product ID etc.,) But when I tried to mount it, it fails. Posting failure details would help; it could just be a config issue, or your use of a kernel too old to know about quirks in your drive. Is there anything I should do make my PCI - USB work on 2.4 kernel ? Did you try 2.4.29? If that doesn't work, I suggest upgrading to a 2.6 kernel ... RH9 works pretty well with that, other than needing upgraded modutils (and maybe more). - Dave --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] PCI - USB - Device fails to enumerate. Roothub works.
Hi, I am using ISP 1561 PCI - USB controller in my project (with MVL 3.1). I am able to configure the root hub with ehci-hcd.o. But it is not enumerating when a device is attached (tried with mouse). When no devices are connected, the /proc/usb/devices lists the root hub's configuration. After a device is connected, it does not display anything more than what it used to display (still just the root hub configuration) . I have attached the kernel messages with this mail for the reference. I have also attached the contents of /proc/usb/devices (log2.txt) and lsmod results (log1.txt) We have added some printks inside the usb_control_msg function for debugging purpose. Thanks, Jayaprakash. 2003-12-25ADS setup arch MPC82xx PCI bridge initialization On node 0 totalpages: 65536 zone(0): 65536 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/nfs rw ip=bootp nfsroot=10.100.131.41:/tftpboot/root init=/bin/sh ADS init IRQ. NR_IRQS=256 PIC: fully preemptible IRQ mode ADS time init ADS calibrate decrementer. FREQ=8000, tb_ticks_per_jiffy=20 Calibrating delay loop... 212.99 BogoMIPS Memory: 257388k available (1136k kernel code, 420k data, 76k init, 0k highmem) Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode cache hash table entries: 16384 (order: 5, 131072 bytes) Mount-cache hash table entries: 4096 (order: 3, 32768 bytes) Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes) Page-cache hash table entries: 65536 (order: 6, 262144 bytes) POSIX conformance testing by UNIFIX PCI: Probing PCI hardware BEFORE RECORDED PCI CONTROLLERS Scanning bus 00 Found 00:00 [1057/18c0] 000600 00 PCI:00:00.0 Resource 0 [-0001] is unassigned PCI:00:00.0 Resource 1 [-1fff] is unassigned Found 00:58 [1131/1561] 000c03 00 PCI:00:0b.0 Resource 0 [-0fff] is unassigned Found 00:59 [1131/1561] 000c03 00 PCI:00:0b.1 Resource 0 [-0fff] is unassigned Found 00:5a [1131/1562] 000c03 00 PCI:00:0b.2 Resource 0 [-00ff] is unassigned Fixups for bus 00 Bus scan for 00 returning with max=00 Bus scan for 00 returning with max=00 AFTER RECORDED PCI CONTROLLERS AFTER PCI BIOS MAKE OF BUS MAP Fixing up Irq for PCI Device (PCI device 1057:18c0) To IRQ 0 Fixing up Irq for PCI Device (PCI device 1131:1561) To IRQ 6 Fixing up Irq for PCI Device (PCI device 1131:1561) To IRQ 6 Fixing up Irq for PCI Device (PCI device 1131:1562) To IRQ 6 After PCI Interrupt Routing PCI: moved device 00:0b.0 resource 0 (200) to 8000 PCI: moved device 00:0b.1 resource 0 (200) to 80001000 PCI: moved device 00:0b.2 resource 0 (200) to 80002000 After PCIBIOS FIXUP PCI: bridge rsrc edfff000..efffefff (100), parent c0141e28 PCI: bridge rsrc 8000..8fff (200), parent c0141e44 PCI: bridge rsrc 9000..9fff (1200), parent c0141e44 AFTER ALLOCATE AND ASSIGN RESOURCES End of PCI INIT ADS init Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket LSP Revision 1 ikconfig 0.5 with /proc/ikconfig Starting kswapd Disabling the Out Of Memory Killer devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x1 i2c-core.o: i2c core module version 2.6.2 (2008) i2c-dev.o: i2c /dev entries driver module version 2.6.2 (2008) i2c-algo-bit.o: i2c bit algorithm module version 2.6.2 (2008) i2c-proc.o version 2.6.2 (2008) pty: 256 Unix98 ptys configured devsoc: devsoc_init: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize loop: loaded (max 8 devices) MPC8260 FCC Ethernet driver devsoc_xcc_create c052 Created eth0 devsoc_xcc_create c050 Created eth1 NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 2048 buckets, 16Kbytes TCP: Hash tables configured (established 16384 bind 32768) eth0: OPEN BD rings initialised, RBASE=538160, TBASE=538360 eth1: OPEN BD rings initialised, RBASE=518160, TBASE=518360 Sending BOOTP requests . OK IP-Config: Got BOOTP answer from 10.100.131.41, my address is 10.100.131.20 eth1: STOP IP-Config: Complete: device=eth0, addr=10.100.131.20, mask=255.255.255.0, gw=10.100.131.1, host=10.100.131.20, domain=, nis-domain=(none), bootserver=10.100.131.41, rootserver=10.100.131.41, rootpath=/tftpboot/root NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Looking up port of RPC 13/2 on 10.100.131.41 Looking up port of RPC 15/1 on 10.100.131.41 VFS: Mounted root (nfs filesystem). Mounted devfs on /dev Freeing unused kernel memory: 76k init usb.c: registered new driver usbdevfs usb.c: registered new driver hub ehci-hcd.c: 2002-May-07 USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-hcd.c: block sizes: qh 96 qtd 96 itd 128 sitd 64 hcd.c: ehci-hcd @ 00:0b.2, PCI device 1131:1562 hcd.c: irq 6, pci mem d1027000 usb.c: new USB bus registered, assigned bus number 1 ehci-dbg.c: ehci_start hcs_params 0x12214 dbg=0 ind cc=2 pcc=2 ordered ports=4
[linux-usb-devel] PCI - USB2.0 RH Works but device fails while SetAddress.
Hi, I am sorry that I sent out the attachments in the last mail. Here they are for your convenience. I am using ISP 1561 PCI - USB controller in my project (with MVL 3.1). I am able to configure the root hub with ehci-hcd.o. But it is not enumerating when a device is attached (tried with mouse). When no devices are connected, the /proc/usb/devices lists the root hub's configuration. After a device is connected, it does not display anything more than what it used to display (still just the root hub configuration) . I have attached the kernel messages with this mail for the reference. I have also attached the contents of /proc/usb/devices (log2.txt) and lsmod results (log1.txt) We have added some printks inside the usb_control_msg function for debugging purpose. Thanks, Jayaprakash. 2003-12-25ADS setup arch MPC82xx PCI bridge initialization On node 0 totalpages: 65536 zone(0): 65536 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/nfs rw ip=bootp nfsroot=10.100.131.41:/tftpboot/root init=/bin/sh ADS init IRQ. NR_IRQS=256 PIC: fully preemptible IRQ mode ADS time init ADS calibrate decrementer. FREQ=8000, tb_ticks_per_jiffy=20 Calibrating delay loop... 212.99 BogoMIPS Memory: 257388k available (1136k kernel code, 420k data, 76k init, 0k highmem) Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode cache hash table entries: 16384 (order: 5, 131072 bytes) Mount-cache hash table entries: 4096 (order: 3, 32768 bytes) Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes) Page-cache hash table entries: 65536 (order: 6, 262144 bytes) POSIX conformance testing by UNIFIX PCI: Probing PCI hardware BEFORE RECORDED PCI CONTROLLERS Scanning bus 00 Found 00:00 [1057/18c0] 000600 00 PCI:00:00.0 Resource 0 [-0001] is unassigned PCI:00:00.0 Resource 1 [-1fff] is unassigned Found 00:58 [1131/1561] 000c03 00 PCI:00:0b.0 Resource 0 [-0fff] is unassigned Found 00:59 [1131/1561] 000c03 00 PCI:00:0b.1 Resource 0 [-0fff] is unassigned Found 00:5a [1131/1562] 000c03 00 PCI:00:0b.2 Resource 0 [-00ff] is unassigned Fixups for bus 00 Bus scan for 00 returning with max=00 Bus scan for 00 returning with max=00 AFTER RECORDED PCI CONTROLLERS AFTER PCI BIOS MAKE OF BUS MAP Fixing up Irq for PCI Device (PCI device 1057:18c0) To IRQ 0 Fixing up Irq for PCI Device (PCI device 1131:1561) To IRQ 6 Fixing up Irq for PCI Device (PCI device 1131:1561) To IRQ 6 Fixing up Irq for PCI Device (PCI device 1131:1562) To IRQ 6 After PCI Interrupt Routing PCI: moved device 00:0b.0 resource 0 (200) to 8000 PCI: moved device 00:0b.1 resource 0 (200) to 80001000 PCI: moved device 00:0b.2 resource 0 (200) to 80002000 After PCIBIOS FIXUP PCI: bridge rsrc edfff000..efffefff (100), parent c0141e28 PCI: bridge rsrc 8000..8fff (200), parent c0141e44 PCI: bridge rsrc 9000..9fff (1200), parent c0141e44 AFTER ALLOCATE AND ASSIGN RESOURCES End of PCI INIT ADS init Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket LSP Revision 1 ikconfig 0.5 with /proc/ikconfig Starting kswapd Disabling the Out Of Memory Killer devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x1 i2c-core.o: i2c core module version 2.6.2 (2008) i2c-dev.o: i2c /dev entries driver module version 2.6.2 (2008) i2c-algo-bit.o: i2c bit algorithm module version 2.6.2 (2008) i2c-proc.o version 2.6.2 (2008) pty: 256 Unix98 ptys configured devsoc: devsoc_init: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize loop: loaded (max 8 devices) MPC8260 FCC Ethernet driver devsoc_xcc_create c052 Created eth0 devsoc_xcc_create c050 Created eth1 NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 2048 buckets, 16Kbytes TCP: Hash tables configured (established 16384 bind 32768) eth0: OPEN BD rings initialised, RBASE=538160, TBASE=538360 eth1: OPEN BD rings initialised, RBASE=518160, TBASE=518360 Sending BOOTP requests . OK IP-Config: Got BOOTP answer from 10.100.131.41, my address is 10.100.131.20 eth1: STOP IP-Config: Complete: device=eth0, addr=10.100.131.20, mask=255.255.255.0, gw=10.100.131.1, host=10.100.131.20, domain=, nis-domain=(none), bootserver=10.100.131.41, rootserver=10.100.131.41, rootpath=/tftpboot/root NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Looking up port of RPC 13/2 on 10.100.131.41 Looking up port of RPC 15/1 on 10.100.131.41 VFS: Mounted root (nfs filesystem). Mounted devfs on /dev Freeing unused kernel memory: 76k init usb.c: registered new driver usbdevfs usb.c: registered new driver hub ehci-hcd.c: 2002-May-07 USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-hcd.c: block sizes: qh 96 qtd 96 itd 128 sitd 64 hcd.c: ehci-hcd @ 00:0b.2, PCI device 1131:1562 hcd.c: irq 6, pci mem d1027000 usb.c: new USB bus registered, assigned
Re: [linux-usb-devel] usb harddisk error when setaddress(USB device not accepting new address=2 (error=-110))
Hi, Me too having similar kind of problem here. I have insmod the usbcore.o and ehci-hcd.o. Now the proc/bus/usb/devices says : T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 4 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.04 S: Manufacturer=Linux 2.4.20_mvl31-8275VR ehci_hcd S: Product=PCI device 1131:1562 S: SerialNumber=00:0b.2 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=256ms When I tried to connect any device, the system fails on SetAddress (Timeout Error) called from usb_new_device() from usb_hub_port_connect_change(). Can anybody help me to come out of this problem ? Thanks, Jayaprakash. On Wed, 23 Feb 2005 12:44:06 +0800, sunnyfaye [EMAIL PROTECTED] wrote: The problem I'm having is that I can't find 40G usb external harddisk in linux. BUT it can find 128m u disk. Why? Can you help me? Thanks When I use u disk, everything is ok. I can mount and use the u disk. When I changed into mobile harddisk, I can't mount it. Both of the mobile harddisk and u disk are usb mass storage. What is the difference between them? I have changed 3 mobile harddisks and one of them has enough power.I'm using MontaVista 3.0 and the kernel is 2.4.20. The pci to usb controller is VT6212.Does it need special usb driver for VT6212? System can detect the controller successfully. the error message is as follows: USB disconnect on device 00:02.0-1 address 2 hub.c: new USB device 00:02.2-1, assigned address 2 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=2 (error=-110) hub.c: new USB device 00:02.2-1, assigned address 3 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=3 (error=-110) CPU: IBM PowerPC 405GP Rev. E at 198 MHz (PLB=66, OPB=16, EBC=33 MHz) PCI async ext clock used, internal PCI arbiter enabled 16 kB I-Cache 8 kB D-Cache BOARD: Cogent CSB272 I2C: ready DRAM: 64 MB FLASH: erase_region_count = 128 erase_region_size = 131072 32 MB In:serial Out: serial Err: serial BEDBUG:ready Hit any key to stop autoboot: 0 ENET Speed is 10 Mbps - HALF duplex connection TFTP from server 10.96.10.215; our IP address is 10.96.10.217 Filename 'uImage_usb_all.bin'. Load address: 0x20 Loading: U-Boot 1.1.1 (Dec 27 2004 - 17:14:19) CPU: IBM PowerPC 405GP Rev. E at 198 MHz (PLB=66, OPB=16, EBC=33 MHz) PCI async ext clock used, internal PCI arbiter enabled 16 kB I-Cache 8 kB D-Cache BOARD: Cogent CSB272 I2C: ready DRAM: 64 MB FLASH: erase_region_count = 128 erase_region_size = 131072 32 MB In:serial Out: serial Err: serial BEDBUG:ready Hit any key to stop autoboot: 0 ENET Speed is 10 Mbps - HALF duplex connection TFTP from server 10.96.10.215; our IP address is 10.96.10.217 Filename 'uImage_usb_all.bin'. Load address: 0x20 Loading: # # # # done Bytes transferred = 1410351 (15852f hex) ## Booting image at 0020 ... Image Name: Linux-2.4.20_mvl31-405gp_eval Created: 2005-01-06 5:30:25 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1410287 Bytes = 1.3 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK Linux version 2.4.20_mvl31-405gp_eval ([EMAIL PROTECTED]) (gcc version 3.2.1 20020930 (MontaVista)) #46 Thu Jan 6 13:29:44 CST 2005 CSB272 (IBM405GP) Platform Port by MontaVista Software, Inc. ([EMAIL PROTECTED]) On node 0 totalpages: 15360 zone(0): 15360 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: console=ttyS0,38400 root=/dev/nfs rw mem=60m nfsroot=10.96. 10.215:/target/rcfs ip=10.96.10.217:10.96.10.215:10.96.10.254:255.255.255.0:CS20 00::off hr_time_init: arch_to_nsec = 10591676, nsec_to_arch = 850403524 Calibrating delay loop... 197.42 BogoMIPS Memory: 57484k available (2236k kernel code, 872k data, 104k init, 0k highmem) Dentry cache hash table entries: 8192 (order: 4, 65536 bytes) Inode cache hash table entries: 4096 (order: 3, 32768 bytes) Mount-cache hash table entries: 1024 (order: 1, 8192 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) POSIX conformance testing by UNIFIX PCI: Probing PCI hardware PCI: Cannot allocate resource region 4 of device 00:02.1 PCI: moved device 00:01.0 resource 0 (101) to 1000 PCI: moved device 00:01.0 resource 1 (101) to 1000 PCI:
[linux-usb-devel] PCI - USB
Hello Everybody, I am working on the PCI-USB card on 2.4. Is there any link that has details of the PCI BIOS fixup routines and the details about PCI resource allocation ? I have ISP 1561 PCI - USB controller on my board (8270 based and running MV Linux 2.4). I was told that the kernel has to assign resources for the PCI device if it is not running on Intel (in which case the BIOS will take care of it). The device I use is the memory mapped device and uses only one BAR (BAR 0). I am not sure how to allocate resources to it. My device requests me 4K memory and I have done the following code in the pcibios_fixup_resources() pcibios_write_config_dword(0,dev-devfn,PCI_BASE_ADDRESS_0,0x8000); dev-resource[0].start = 0x8000; dev-resource[0].end = dev-resource[0].start+0xfff Is this OK ? Or Do I need to relocate this memory using ioremap() ? Thanks Regards, Jayaprakash. --- 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=6595alloc_id=14396op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Open USB Device
Hi All,
I am new to USB world. I have a basic doubt. I wrote the USB
driver by going through some tutorials. I compiled it and inmod it
without any problems. Now, If I want to use my driver, I need a major
number. There I got stuck up. I didnt have any major number used in
my driver. So, how to open the USB device ? Can anybody be of any
help ? Here is my Init and CleanUp functions where I dont have any
major numbers used.
static int __init USBH__iInit()
{
int Result;
/* Register the driver with the USB subsystem */
Result = usb_register(USBH__stApplDriver);
if (Result 0)
{
printk(KERN_ERR usb_register failed for the USB Application \
Driver: Error Number = %d,Result);
return -1;
}
return 0;
}
static void __exit USBH__vExit(void)
{
/* Deregister the driver from the USB subsystem */
usb_deregister(USBH__stApplDriver);
}
module_init(USBH__iInit);
module_exit(USBH__vExit)
Regards,
Jayaprakash.
---
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=6595alloc_id=14396op=click
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Open USB Device
Thanks to Oliver and Shalini for your replies. I did devfs_register
in my probe and I was able to open the device.
On Sat, 12 Mar 2005 12:26:30 +0530, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi Jayaprakash,
In linux system, USB devices are identified by major number 180, so you
need to create device node with major no 180 and minor no (mknod usbdrv
180 0)
While registering device driver you don't have to give major as such,
you need to mention only minor number. All these information, you need
to define it in the USB driver structure (e.g, USBH__stApplDriver).
If you say open it will check minor number and open the device file.
One more suggestion is go thru USB code in Linux.
I hope you understand this.
Regards,
Shalini G
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jayaprakash Shanmugam
Sent: Saturday, March 12, 2005 2:21 AM
To: linux-usb-devel@lists.sourceforge.net
Subject: [linux-usb-devel] Open USB Device
Hi All,
I am new to USB world. I have a basic doubt. I wrote the USB
driver by going through some tutorials. I compiled it and inmod it
without any problems. Now, If I want to use my driver, I need a major
number. There I got stuck up. I didnt have any major number used in
my driver. So, how to open the USB device ? Can anybody be of any
help ? Here is my Init and CleanUp functions where I dont have any
major numbers used.
static int __init USBH__iInit()
{
int Result;
/* Register the driver with the USB subsystem */
Result = usb_register(USBH__stApplDriver);
if (Result 0)
{
printk(KERN_ERR usb_register failed for the USB
Application \
Driver: Error Number = %d,Result);
return -1;
}
return 0;
}
static void __exit USBH__vExit(void)
{
/* Deregister the driver from the USB subsystem */
usb_deregister(USBH__stApplDriver);
}
module_init(USBH__iInit);
module_exit(USBH__vExit)
Regards,
Jayaprakash.
---
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=6595alloc_id=14396op=click
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Confidentiality Notice
The information contained in this electronic
message and any attachments to this message are
intended for the exclusive use of the addressee(s)
and may contain confidential or privileged information.
If you are not the intended recipient, please notify
the sender at Wipro or [EMAIL PROTECTED] immediately
and destroy all copies of this message and any attachments.
---
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=6595alloc_id=14396op=click
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Unrecoverable Error
Hi Group, I use PCI-USB ISP 1561 with 2.4 Kernel. It has got 2 OHCI and 1 EHCI. When I insmod usb-ohci.o it says Unrecoverable error and gets out. I did check my UE bit in the interrupt status register of the OHCI and it is set. The error gets printed from the hc_interrupt() in the usb-ohci.c. Do you have any idea of how to tackle this problem ? Does it have anything to do with my DMA or PCI settings ? Thanks, Jayaprakash. --- 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=6595alloc_id=14396op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Unrecoverable Error
Thanks David. I am one of the victims of Monta Vista. On Sat, 12 Mar 2005 08:22:27 -0800, David Brownell [EMAIL PROTECTED] wrote: On Saturday 12 March 2005 5:38 am, Jayaprakash Shanmugam wrote: Hi Group, I use PCI-USB ISP 1561 with 2.4 Kernel. It has got 2 OHCI and 1 EHCI. When I insmod usb-ohci.o it says Unrecoverable error and gets out. I did check my UE bit in the interrupt status register of the OHCI and it is set. The error gets printed from the hc_interrupt() in the usb-ohci.c. Do you have any idea of how to tackle this problem ? Does it have anything to do with my DMA or PCI settings ? It's usually caused by a bad pointer in an ED or TD. The 2.4 kernel has lots of bugs that are now fixed in 2.6 ... try using more current code, it probably is fixed already. --- 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=6595alloc_id=14396op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Device not accepting address with EHCI-HCD
Hi All, I have a strange behavior here with my ISP 1561 PCI-USB card. 1) When I plug in our board (USB based), it works fine with OHCI (the PCI USB card has 2 OHCI and 1 EHCI core). 2) When I try to use the EHCI driver for this board, the device is not accepting the address. It says the protocol error (-EPROTO). Can any of you give me some pointers to trace it out ? Note : I am sure that the board is USB 2.0 capable. The EHCI driver is also good as it goes fine with the USB 2.0 pen drives. Thanks, Jayaprakash --- 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=6595alloc_id=14396op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] How to find out the device's operating speed
Hi Group, Can any of you tell me how to find out the USB speed at which the device is operating on ? I can get it from the /proc/bus/usb/devices. I guess the information put up there is taken from the descriptors given by the device. But how can I make sure that the descriptors given by the device is right ? Thanks, Jayaprakash. --- 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=6595alloc_id=14396op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] USB Int Transfer - How ?
Hello All, I am using 2.4 based kernel. I have a usb device connected to the host. The device will send data to me over the interrupt endpoint. The host has to capture the data do some processing. I have a module in which I use the following code in the read function : FILL_INT_URB(urb, pstUSBDev, pipe, pcData, maxp, IRQHandler, 0 , bInterval); usb_submit_urb(urb); Now my issue here is: What should I do inside the IRQHandler( ) ? If I do nothing in the handler, Can I be able to read the data from the user mode ? Any suggestions would be greatly helpful. Thanks, Jayaprakash. --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] VID PID based fixed minor numbers - How ?
Hello All,
I have a USB driver that talks to four devices differentiated by their
minor numbers (fixed minor numbers for everyone of the devices)
In 2.4 Kernel - Probe () function :
I used devfs_register() for all the devices as follows:
for (i =0; i = 4;i++)
{
devfs_register(usb_devfs_handle, MyDriver,DEVFS_FL_DEFAULT,USB_MAJOR,
USBH_MINOR_BASE+i,S_IFCHR | S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP, Fops, NULL);
}
I have this code working and planning to migrate to 2.6 kernel.
In 2.6 kernel :
When I looked into the usb-skeleton.c, it is suggested to use the
usb_register_dev() function. My problem here is this function
allocates minor numbers automatically starting from the base and I
dont have control over it ? For eg., If I plug in card 1 and then card
2, I will have minors as 64 for Card 1 and 65 for card 2. If I plug
in card 2 and then card 1, I will have minors as 64 for card 2 and 65
for card 1.
Could you please help me to fix a minor number based on the vendor ID
and product ID of a card ?
Thanks Regards
Jayaprakash.
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] VID PID based fixed minor numbers - How ?
I have one driver serving 4 devices at a time. Can't I have one fixed
minor number for one device ?
When read() / write() into the device, how can I know which device I
am operating on ? Right now (in 2.4) I use the minor number of the
node to find out which one I am working on. Please bear with me, if
this is trivial.
On 7/5/05, Greg KH [EMAIL PROTECTED] wrote:
On Tue, Jul 05, 2005 at 07:39:49PM +0530, Jayaprakash Shanmugam wrote:
Thanks for your reply. I just wanted to give some more information on
my requirement.
1) In my driver (working in 2.4), I have fixed minor numbers for the
USB cards (custom devices). While reading or writing, I simply do the
following:
MyCard = MINOR (pstFilp-f_dentry-d_inode-i_rdev);
if (MyCard == 64)
{
MyDevice = usb_find_device(MyCardVID, MyCardPID);
usb_control_msg();
}
else if ()
..
But if I use usb_register_dev(), it assigns the minors dynamically and
no way ( as far as I know ) I can get which device ( I have four
devices and I am sure that they will not have PIDs in common ) the
read / write is operating on.
You can check the minor number when you register the device. It is
returned in the structure after usb_register_dev() is called.
2) For your reply:
It is our own control system - both the host and devices. These are
the only devices that can go and plug into the host's USB port.
There cannot be two boards with same VID / PID pair.
3) Can I use devfs_register in 2.6 kernel ? The /proc/kallsyms doesnt
display this symbol. I tried using devfs_mk_cdev() in probe. But I
got No Such Device while opening.
devfs is gone in the latest 2.6 kernel, so no, you can't use it.
Good luck,
greg k-h
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: VID PID based fixed minor numbers - How ?
Yes. Thats correct. Thanks for your suggestion. I will try it out. Currently I am stuck up in probe(). I have two devices for one driver. The kernel reports error when it probes for the second device. While my first device is plugged in, it didnt complain anything. But it reports BUG if I plug in the second device as follows: devfs_mk_dev: could not append to parent for USBHClassDriver kernel BUG in sysfs_create_file at fs/sysfs/file.c:381! Oops: Exception in kernel mode, sig: 5 [#1] PREEMPT NIP: C009A580 LR: C012381C SP: C0783D30 REGS: c0783c80 TRAP: 0700Not tainted MSR: 00029032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 TASK = c054d3d0[35] 'khubd' THREAD: c0782000 Last syscall: -1 GPR00: 0001 C0783D30 C054D3D0 C0267230 C009A8F4 CF2BAFDE 000A GPR08: 0001 0001 24008024 0FFFE000 GPR16: 0001 0001 C026 C015 C021 CF0D1260 C021 C01F GPR24: 0001 C01F FFED CF4AE760 0040 D106C118 CFF81C20 NIP [c009a580] sysfs_create_file+0x2c/0x40 LR [c012381c] class_device_create_file+0x20/0x38 Call trace: [c0152074] usb_register_dev+0x164/0x198 [d1069d20] USBH__iProbe+0x4c/0xf8 [USBH1C1] [c0146bac] usb_probe_interface+0xd8/0x108 [c0122544] driver_probe_device+0x4c/0xa0 [c01225f0] device_attach+0x58/0xe0 [c01229d8] bus_add_device+0x7c/0xe4 [c0121048] device_add+0xd8/0x18c [c01507b0] usb_set_configuration+0x2dc/0x434 [c014a2ec] usb_new_device+0x110/0x200 [c014b610] hub_port_connect_change+0x340/0x528 [c014bc38] hub_events+0x440/0x548 [c014bd80] hub_thread+0x40/0xe8 [c00064a4] kernel_thread+0x44/0x60 I do the following in Probe: retval = usb_register_dev(interface, USBH__stClassDriver); and I call usb_register() in my init(). Regards, Jayaprakash On 7/11/05, Ian Abbott [EMAIL PROTECTED] wrote: On 09/07/2005 03:50, Greg KH wrote: On Thu, Jul 07, 2005 at 09:20:44PM +0530, Jayaprakash Shanmugam wrote: I have one driver serving 4 devices at a time. Can't I have one fixed minor number for one device ? When read() / write() into the device, how can I know which device I am operating on ? Get the pointer to the device that is associated with that minor number. See the usb-skeleton driver as an example. Greg, I think Jayaprakash wants to asociate the minor number with a physical device at user level. I think he needs pointing towards the udev tutorials! Jayprakash, If possible, you could use four fixed USB serial numbers, one for each device in a set, and write udev rules to automatically create (and destroy) symlinks to each device, based on their serial number. The minor device numbers will change depending on the order you plug in the devices, but the symlink names will still match the physical device no matter which minor device number it ends up with. Use the symlinks to open the device. If your driver needs to treat the four devices differently from each other, implement an ioctl so that the application can inform the driver which device has which rôle. -- -=( Ian Abbott @ MEV Ltd.E-mail: [EMAIL PROTECTED])=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=- --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: VID PID based fixed minor numbers - How ?
I got this problem fixed by giving class_driver.name=driver-%d. Earlier I didnt have the %d with my name. On 7/11/05, Jayaprakash Shanmugam [EMAIL PROTECTED] wrote: Yes. Thats correct. Thanks for your suggestion. I will try it out. Currently I am stuck up in probe(). I have two devices for one driver. The kernel reports error when it probes for the second device. While my first device is plugged in, it didnt complain anything. But it reports BUG if I plug in the second device as follows: devfs_mk_dev: could not append to parent for USBHClassDriver kernel BUG in sysfs_create_file at fs/sysfs/file.c:381! Oops: Exception in kernel mode, sig: 5 [#1] PREEMPT NIP: C009A580 LR: C012381C SP: C0783D30 REGS: c0783c80 TRAP: 0700Not tainted MSR: 00029032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 TASK = c054d3d0[35] 'khubd' THREAD: c0782000 Last syscall: -1 GPR00: 0001 C0783D30 C054D3D0 C0267230 C009A8F4 CF2BAFDE 000A GPR08: 0001 0001 24008024 0FFFE000 GPR16: 0001 0001 C026 C015 C021 CF0D1260 C021 C01F GPR24: 0001 C01F FFED CF4AE760 0040 D106C118 CFF81C20 NIP [c009a580] sysfs_create_file+0x2c/0x40 LR [c012381c] class_device_create_file+0x20/0x38 Call trace: [c0152074] usb_register_dev+0x164/0x198 [d1069d20] USBH__iProbe+0x4c/0xf8 [USBH1C1] [c0146bac] usb_probe_interface+0xd8/0x108 [c0122544] driver_probe_device+0x4c/0xa0 [c01225f0] device_attach+0x58/0xe0 [c01229d8] bus_add_device+0x7c/0xe4 [c0121048] device_add+0xd8/0x18c [c01507b0] usb_set_configuration+0x2dc/0x434 [c014a2ec] usb_new_device+0x110/0x200 [c014b610] hub_port_connect_change+0x340/0x528 [c014bc38] hub_events+0x440/0x548 [c014bd80] hub_thread+0x40/0xe8 [c00064a4] kernel_thread+0x44/0x60 I do the following in Probe: retval = usb_register_dev(interface, USBH__stClassDriver); and I call usb_register() in my init(). Regards, Jayaprakash On 7/11/05, Ian Abbott [EMAIL PROTECTED] wrote: On 09/07/2005 03:50, Greg KH wrote: On Thu, Jul 07, 2005 at 09:20:44PM +0530, Jayaprakash Shanmugam wrote: I have one driver serving 4 devices at a time. Can't I have one fixed minor number for one device ? When read() / write() into the device, how can I know which device I am operating on ? Get the pointer to the device that is associated with that minor number. See the usb-skeleton driver as an example. Greg, I think Jayaprakash wants to asociate the minor number with a physical device at user level. I think he needs pointing towards the udev tutorials! Jayprakash, If possible, you could use four fixed USB serial numbers, one for each device in a set, and write udev rules to automatically create (and destroy) symlinks to each device, based on their serial number. The minor device numbers will change depending on the order you plug in the devices, but the symlink names will still match the physical device no matter which minor device number it ends up with. Use the symlinks to open the device. If your driver needs to treat the four devices differently from each other, implement an ioctl so that the application can inform the driver which device has which rôle. -- -=( Ian Abbott @ MEV Ltd.E-mail: [EMAIL PROTECTED])=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=- --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Control transfer for reading unknown size
Hello All, I use control transfer to read some bytes of data from a device. But I dont know how much data it is going to give me. If I give less number of bytes as size, the usb_control_msg() function skips data (returns when the size number of bytes is read). If I give more number of bytes as size, the usb_control_msg() function returns timeout error. Is there any way to read n number of bytes from the device (using control transfer) when n is not known apriori ? Note: If I use usb_bulk_msg() with size = 1024, it always returns even if there is less number of data. Regards, Jayaprakash. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] USB issues : Device not accepting address
Is it your custom board ? Did you try with USB 1.1 ? In our case, it gives protocol error (-71) in USB 2.0 and works fine in USB 1.1. On 7/11/05, Ram [EMAIL PROTECTED] wrote: I can do ifconfig usb0 and assign an address to my usb0. But, why the device addess given by the host is not being accepted by my gadget. Please Advice. Regards, Ram On 7/10/05, Alan Stern [EMAIL PROTECTED] wrote: On Sun, 10 Jul 2005, Ram wrote: Hi, When i connect my device (ethernet gadget) into the host. i get the message when i do dmesg on host. usbcore: registered new driver usbnet usb 2-2: new full speed USB device using address 6 usb 2-2: device not accepting address 6, error -71 usb 2-2: new full speed USB device using address 7 usb 2-2: device not accepting address 7, error -71 Googling did not help much. cant make out what the problem is all about and how to resolve it. Please advice. The error messages mean that your device does not respond to the USB Set-Address request. The debugging log on the gadget may contain more information. Alan Stern --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] USB 2.0 Enumeration Intermittent
Hello All, We have our custom board (running on 2.6) on which a USB Hub ( Philips ISP 1521 ) connected to the Ehci-controller ( Philips ISP 1561) . When we insmod ohci-hcd, the hub enumerates properly as 1.1 device. When we insmod ehci-hcd, the hub sometimes enumerates as 2.0 device. But most of the times it gives protocol error (-71) while reading the device descriptor. Is it because of hardware issue ? Any inputs / pointers would be very much helpful to me. Thanks, Jayaprakash. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] USB 2.0 Bulk Transfer 1024 Bytes fails.
Hi All, We have a ISP 1561 based USB host (supports both ohci and ehci) in our board. When we have the ohci drivers for this host, we were able to transfer 1024 bytes of bulk data from the device connected to it. But, when we read the bulk data (1024 bytes) with ehci drivers installed, it returns EOVERFLOW error. Can any of you help me to fix this up ? Is this a limitation with USB 2.0 EHCI drivers ??? Note: I am using kernel 2.6. Thanks Regards, Jayaprakash. --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Interrupt Handler on 2.6 called just once
Hi all,
I had a code that receives interrupt data from the device. It
worked with 2.4 kernel. I migrated to 2.6 kernel and it now calls the
Interrupt handler just once.
On 2.4, I had the following and it was working. I got my
USBH__vIRQHandler() function called for every 200 milliseconds.
static int USBH__iStartIntRead(struct usb_device *pstUSBDev,char
*pcData,int iLen,\
int *piCount, int iTimeout)
{
int pipe, maxp, ret;
urb = usb_alloc_urb(0);
if (!urb)
return -ENOMEM;
pipe = usb_rcvintpipe(pstUSBDev,USBH_INT);
maxp = usb_maxpacket(pstUSBDev, pipe, usb_pipeout(pipe));
FILL_INT_URB(urb, pstUSBDev, pipe, pcData, maxp,\
USBH__vIRQHandler, stTCStatus , 200);
//printk(Submitting URB\n);
ret = usb_submit_urb(urb);
printk(KERN_INFO INT URB Submitted\n);
return ret;
}
static void USBH__vIRQHandler(struct urb *IntUrb,struct pt_regs *pRegs)
{
//printk(KERN_INFO Interrupt Handler Called\n);
if (IntUrb-status != USBH_ST_NOERROR)
return;
pstTCStatus = IntUrb-transfer_buffer;
NewData++;
return;
}
On 2.6, I have the following code, but the interrupt handler is called
just once.
static int USBH__iStartIntRead(struct usb_device *pstUSBDev,char
*pcData,int iLen,\
int *piCount, int iTimeout)
{
int pipe, maxp, ret;
urb = usb_alloc_urb(0,GFP_KERNEL);
if (!urb)
return -ENOMEM;
pipe = usb_rcvintpipe(pstUSBDev,USBH_INT);
maxp = usb_maxpacket(pstUSBDev, pipe, usb_pipeout(pipe));
usb_fill_int_urb(urb, pstUSBDev, pipe, pcData, maxp,\
USBH__vIRQHandler, stTCStatus , 200);
//printk(Submitting URB\n);
ret = usb_submit_urb(urb,GFP_KERNEL);
printk(KERN_INFO INT URB Submitted: %d\n,ret);
return ret;
}
static void USBH__vIRQHandler(struct urb *IntUrb,struct pt_regs *pRegs)
{
//printk(KERN_INFO Interrupt Handler Called\n);
if (IntUrb-status != USBH_ST_NOERROR)
return;
pstTCStatus = IntUrb-transfer_buffer;
NewData++;
return;
}
Could you please let me know if there is anything wrong in my code ?
Thanks and Regards,
Jayaprakash.
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42 plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Interrupt Handler on 2.6 called just once
Thank you David and Alan for clarifying it. On 11/9/05, Alan Stern [EMAIL PROTECTED] wrote: On Wed, 9 Nov 2005, Jayaprakash Shanmugam wrote: Hi all, I had a code that receives interrupt data from the device. It worked with 2.4 kernel. I migrated to 2.6 kernel and it now calls the Interrupt handler just once. On 2.4, I had the following and it was working. I got my USBH__vIRQHandler() function called for every 200 milliseconds. ... On 2.6, I have the following code, but the interrupt handler is called just once. ... Could you please let me know if there is anything wrong in my code ? That's a loaded question. There's nothing wrong with your code if you want your handler function called only once. :-) If you want the interrupt URB to be resubmitted after every completion, you have to do so yourself. Unlike 2.4, Linux 2.6 does not support automatic resubmission of interrupt URBs. Alan Stern --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] USB enumeration - host restart doesn't work.
Hi All, I have a MPC 8270 based board on which a Philips based ISP 1561 ( PCI - USB ) connected to it. I have a self powered device connected to the host. Whenever I restart the host alone, the device fails to enumerate and returns -71 (EPROTO) error. However, if I switch off both the host and device and turn them on again, I got the device enumerated properly. I am not sure what is wrong. Any pointers would be greatly helpful. Thanks, Jayaprakash. --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28alloc_id845op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] device not accepting address
-110 is the timeout error and your device it not accepting the SetAddress itself. What is your device ? On 12/7/05, driversbin driversbin [EMAIL PROTECTED] wrote: Hi, I am using a usb host-host cable from prolific (vendor id=0x067 product id=0x2501) . When I plug-in and out twice I start getting messages like the one below. usb 1-2: device not accepting address 4, error -110 usb 1-2: new full speed USB device using s3c2410-ohci and address 5 usb 1-2: device not accepting address 5, error -110 and device fails to get recognised. How can we solve this? Is it something wrong in the way we are trying to handle the device or is it with the hub driver? any help please Regards :-) __ Yahoo! DSL – Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] rh_report_status crashes
Hello Everyone, I am using MPC 8270 based board with 2.6. It crashes at times. Sometimes the crash is from USB Host module. I have attached several crash reports here. Anybody can give me some pointers on what could be wrong ? I use control, bulk and interrupt endpoints in my application. Oops: kernel access of bad area, sig: 11 [#1] PREEMPT NIP: C013CAF8 LR: C013CCC4 SP: C06FDCA0 REGS: c06fdbf0 TRAP: 0300Not tainted MSR: 1032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11 DAR: 00C12048, DSISR: 2000 TASK = c05d7b30[495] 'CCMsgHndlrExe' THREAD: c06fc000 Last syscall: 54 GPR00: 0001 C06FDCA0 C05D7B30 CF64F0F0 CFAF 0004DC93 C028 C028AC8C GPR08: 00200200 00C12000 00C12048 CF64F0F0 2010C022 1003811C 0FFF8000 GPR16: 0001 7B30 10016EB9 0001 1001751C 10001694 1000E668 GPR24: C029 0001 CF64F000 CFAF CF64F0F0 1032 CF64F000 NIP [c013caf8] roothub_a+0xc/0x6c LR [c013ccc4] ohci_hub_status_data+0xa4/0x1a8 Call trace: [c0130978] rh_report_status+0x12c/0x164 [c0029460] run_timer_softirq+0x120/0x228 [c0024068] __do_softirq+0xd0/0xd8 [c00240c8] do_softirq+0x58/0x5c [c002419c] irq_exit+0x54/0x58 [c0005668] timer_interrupt+0x1ec/0x22c [c000448c] ret_from_except+0x0/0x14 [d106f5a8] FD_ioctl+0x2160/0x35a8 [FDAC1] [c007375c] do_ioctl+0x84/0xac [c00739e8] vfs_ioctl+0x88/0x2c8 [c0073c6c] sys_ioctl+0x44/0x78 [c0003de0] ret_from_syscall+0x0/0x44 Kernel panic - not syncing: Aiee, killing interrupt handler! 0Rebooting in 180 seconds.. # Oops: kernel access of bad area, sig: 11 [#1] PREEMPT NIP: C00288C0 LR: C00289FC SP: CF493C80 REGS: cf493bd0 TRAP: 0300Not tainted MSR: 1032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11 Oops: kernel access of bad are a, sig: 11 [#1] PREEMPT NIP: C0018F24 LR: C001A174 SP: CF415E90 REGS: cf415de0 TRAP: 0300Not tainted MSR: 1032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11 DAR: 00C15C74, DSISR: 2200 TASK = c05d7b30[549] 'CCMsgHndlrExe' THREAD: cf414000 Last syscall: 104 GPR00: 0078 CF415E90 C05D7B30 C05D7B30 C02858AC 2800046C C02858B0 GPR08: 00C15C74 0001 C05D7B50 008C B4868000 1003811C 0FFF8000 GPR16: 0001 7B30 10016EB9 0001 1001751C 10001694 1000E668 GPR24: C029 C028 C02820A8 C028 C0285400 C05D7B30 CF415E90 NIP [c0018f24] enqueue_task+0x34/0x7c LR [c001a174] scheduler_tick+0x300/0x360 Call trace: [c0019c18] account_user_time+0x78/0xe8 [c002924c] update_process_times+0x98/0x150 [c0005504] timer_interrupt+0x88/0x22c [c000448c] ret_from_except+0x0/0x14 Kernel panic - not syncing: Aiee, killing interrupt handler! 0Rebooting in 180 seconds.. Oops: kernel access of bad are a, sig: 11 [#1] PREEMPT NIP: C0018F24 LR: C001A174 SP: CF415E90 REGS: cf415de0 TRAP: 0300Not tainted MSR: 1032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11 DAR: 00C15C74, DSISR: 2200 TASK = c05d7b30[549] 'CCMsgHndlrExe' THREAD: cf414000 Last syscall: 104 GPR00: 0078 CF415E90 C05D7B30 C05D7B30 C02858AC 2800046C C02858B0 GPR08: 00C15C74 0001 C05D7B50 008C B4868000 1003811C 0FFF8000 GPR16: 0001 7B30 10016EB9 0001 1001751C 10001694 1000E668 GPR24: C029 C028 C02820A8 C028 C0285400 C05D7B30 CF415E90 NIP [c0018f24] enqueue_task+0x34/0x7c LR [c001a174] scheduler_tick+0x300/0x360 Call trace: [c0019c18] account_user_time+0x78/0xe8 [c002924c] update_process_times+0x98/0x150 [c0005504] timer_interrupt+0x88/0x22c [c000448c] ret_from_except+0x0/0x14 Kernel panic - not syncing: Aiee, killing interrupt handler! 0Rebooting in 180 seconds. # Oops: kernel access of bad area, sig: 11 [#1] PREEMPT NIP: C0018F24 LR: C001A150 SP: CF415D70 REGS: cf415cc0 TRAP: 0300Not tainted MSR: 1032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11 DAR: 00C1580C, DSISR: 2200 TASK = c0525b30[495] 'CCMsgHndlrExe' THREAD: cf414000 Last syscall: 54 GPR00: CF415D70 C0525B30 C0525B30 C0285434 0001 100300EA C0285438 GPR08: 00C1580C 0001 C0525B50 0076 DB718800 1003807C 0FFF8000 GPR16: 0001 7B30 10016EB9 0001 1001751C 10001694 1000E5C8 GPR24: C029 C028 C02820A8 C028 C0285400 C0525B30 CF415D70 NIP [c0018f24] enqueue_task+0x34/0x7c LR [c001a150] scheduler_tick+0x2dc/0x360 Call trace: [c0019cf0] account_system_time+0x68/0x144 [c002924c] update_process_times+0x98/0x150 [c0005504] timer_interrupt+0x88/0x22c [c000448c] ret_from_except+0x0/0x14 [c00739e0] vfs_ioctl+0x80/0x2c8 [c0073c6c] sys_ioctl+0x44/0x78 [c0003de0] ret_from_syscall+0x0/0x44 Kernel panic - not syncing: Aiee, killing interrupt handler! 0Rebooting in 180 seconds. # Oops: kernel access of bad
[linux-usb-devel] Bulk Transfer fails in USB 2.0
Hi All, I face a different scenario where the software on the host works if the device is in USB 1.1. If the device is configured as USB 2.0, the bulk_read from the device returns EOVERFLOW error. I am running 2.6.11 and the host has 2 EHCI cores and 1 OHCI core. ( Philips ISP 1561 ). The device is supposed to transfer 772 bytes of data over bulk end point. I was able to read 36 bytes ( just tried it ) without any issues even in USB 2.0. Is there any specific sequence the host needs to follow to read bulk endpoint ( when the expected data is more ) Any comments on the above ??? Thank you, Jayaprakash --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] 64 Bit Linux - USB KB
Hello All, I have 64 bit Linux connected to a USB KB emulator ( Cypress based USB device - Works as a KB in Windows 32/64 bits). Though the firmware gets enumerated as a HID device, the keystrokes are not received by the operating system. Is there any suggestion for me ? Thanks in advance. Regards, Jayaprakash. log Description: Binary data log2 Description: Binary data
[linux-usb-devel] USBKB Emulation not working
Hi, We have a Cypress based usb keyboard software that enumerates as a USB Keyboard and works properly in Windows 32 / 64 bit platforms. When it is connected to Linux, the device enumerates as a keyboard with proper configurations. But whatever keystrokes we send to the host are lost. I have attached the dmesg and some more information in the attached log. Do you have any suggestions for it ? Thanks, Jayaprakash. Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 0fefc000 (usable) BIOS-e820: 0fefc000 - 0feff000 (ACPI data) BIOS-e820: 0feff000 - 0ff0 (ACPI NVS) BIOS-e820: - 0001 (reserved) 0MB HIGHMEM available. 254MB LOWMEM available. On node 0 totalpages: 65276 zone(0): 4096 pages. zone(1): 61180 pages. zone(2): 0 pages. Kernel command line: ro root=LABEL=/1 Initializing CPU#0 Detected 936.671 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 1867.77 BogoMIPS Memory: 251984k/261104k available (1347k kernel code, 6696k reserved, 999k data, 132k init, 0k highmem) Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode cache hash table entries: 16384 (order: 5, 131072 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes) Page-cache hash table entries: 65536 (order: 6, 262144 bytes) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: 0383f9ff CPU: Common caps: 0383f9ff CPU: Intel Pentium III (Coppermine) stepping 0a Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.40 (20010327) Richard Gooch ([EMAIL PROTECTED]) mtrr: detected mtrr type: Intel PCI: PCI BIOS revision 2.10 entry at 0xf08b0, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware Transparent bridge - Intel Corp. 82801AA PCI Bridge PCI: Using IRQ router PIIX [8086/2410] at 00:1f.0 isapnp: Scanning for PnP cards... isapnp: No Plug Play device found Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16) Starting kswapd VFS: Disk quotas vdquot_6.5.1 pty: 2048 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled ttyS0 at 0x03f8 (irq = 4) is a 16550A ttyS1 at 0x02f8 (irq = 3) is a 16550A Real Time Clock Driver v1.10e floppy0: no floppy controllers found NET4: Frame Diverter 0.46 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH: IDE controller at PCI slot 00:1f.1 ICH: chipset revision 2 ICH: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:pio, hdd:DMA hda: Maxtor 2B020H1, ATA DISK drive hdb: Maxtor 2F040J0, ATA DISK drive blk: queue c03c9f40, I/O limit 4095Mb (mask 0x) blk: queue c03ca084, I/O limit 4095Mb (mask 0x) hdd: CRD-8483B, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: host protected area = 1 hda: 40020624 sectors (20491 MB) w/2048KiB Cache, CHS=2491/255/63, UDMA(66) hdb: host protected area = 1 hdb: 80293248 sectors (41110 MB) w/2048KiB Cache, CHS=4998/255/63, UDMA(66) ide-floppy driver 0.99.newide Partition check: hda: hda1 hda2 hda3 hdb: hdb1 hdb2 hdb3 ide-floppy driver 0.99.newide md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 2048 buckets, 16Kbytes TCP: Hash tables configured (established 16384 bind 32768) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 145k freed VFS: Mounted root (ext2 filesystem). Journalled Block Device driver loaded kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Freeing unused kernel memory: 132k freed usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.275 $ time 17:59:01 Mar 13 2003
[linux-usb-devel] usbkb - does not work
Hi, We have a Cypress based usb keyboard software that enumerates as a USB Keyboard and works properly in Windows 32 / 64 bit platforms. When it is connected to Linux, the device enumerates as a keyboard with proper configurations. But whatever keystrokes we send to the host are lost. I have attached the dmesg and some more information in the attached log. Do you have any suggestions for it ? Thanks, Jayaprakash. usbkb.log Description: Binary data ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] EHCI - unlink message
Hello All, I am using Philips ISP 1561 PCI - USB with PQ2FADS based board. I have a couple of USB devices connected to it. Both of them are working in high speed. In one of the devices, every 10ms bulk read request is called. The console prints the following message continuously. Can you help us on what could be wrong ? Thanks, Jayaprakash. ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] ehci_hcd :00:0b.2: reused qh c05e3280 schedule usb 1-4: link qh16-0001/c05e3280 start 15 [17/0 us] usb 1-4: unlink qh16-0001/c05e3280 start 15 [17/0 us] - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere
[linux-usb-devel] EP-0 returns timeout even when data is received by the device.
Hi All, I have a EHCI host connected to 4 USB devices (dev1, dev2, dev3 and dev4). I have two processes that make use of these devices through a kernel object. I have some vendor commands (through EP-0) to all the devices. Apart from this, dev1 has EP2 ( in ) bulk, dev2 has EP2 ( in ) interrupt and dev4 has EP6 ( out ) bulk. There are 3 processes in our system. From Process1, I read EP2 from dev1 periodically (for every 30 ms) and send it to EP6 of dev4. The other process Process2, reads the EP2 interrupt endpoint of dev2 periodically. The last process Process3, tries to write to dev4 EP-0 quite frequently (every 3 seconds). Sometimes, the usb_control_msg() receives timeout error. I am not able to understand why it should return timeout error intermittently. 1) When the control endpoint and bulk endpoint are used in a device, Can I not use both of them simultaneously ? 2) When I tried to write to EP-0 of a device, the other process who sends periodic data to EP-2 of the same device receives the error message - ep0out timeout error. Why should the process receive this debug message (from the timeout handler in the usb_submit_urb() ) 3) When I tried to write to EP-0 of a device (while the other process sending data to EP-2 of the same device periodically), the device received the data succesfully. But, the host says the request is timeout. Does it mean that the ACK for the EP-0 packet is received by the URB who waits for ACK for the Bulk transfer. This mail may be huge. Since I am not able to understand the behavior I wanted to give the full details of the issue. Note: I am running Linux 2.6 on MPC 8270 with Philips PCI - USB converter Thanks, Jayaprakash. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] usb_control_msg() returns timeout !!
Hello Group, I have two devices connected to a host. I periodically read bulk data from first device and pass it on to the second device via EP-2. Apart from this periodic data, the host sends some vendor commands through EP-0 of first device. Though these vendor commands are received successfully by the device, usb_control_msg() returns -ETIMEDOUT error sometimes. If I stop sending the periodic bulk data, no -ETIMEDOUT is seen for the usb_control_msg(). I traced out the message.c file and it looks like the URB times out to call the timeout_kill() function. I even tried with a higher timeout, but no improvement is seen. Any pointers on what could have gone wrong ? I observed the same with both EHCI and OHCI drivers. The device is Cypress based, capable of USB2.0. The host runs 2.6.11 on MPC8270 with PCI-USB ISP1561. Regards, Jayaprakash. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
