Re: [linux-usb-devel] Usb storage mount problem
Hi,
I am using my usb controller driver in host mode for mass torage
emulation.
Mass torage device is detected and I got following prints
/ # INQUIRY message sent
Vendor: Generic Model: Flash D Rev:
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdb: 1024 512-byte hdwr sectors (1 MB)
sdb: Write Protect is off
sdb: assuming drive cache: write through
SCSI device sdb: 1024 512-byte hdwr sectors (1 MB)
sdb: Write Protect is off
sdb: assuming drive cache: write through
sdb:7usb-storage: queuecommand called
unknown partition table
sd 1:0:0:0: Attached scsi removable disk sdb
sd 1:0:0:0: Attached scsi generic sg1 type 0
INQUIRY message sent
Vendor: Generic Model: AUTORUN DiskRev: 8.00
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdc: 1024 512-byte hdwr sectors (1 MB)
sdc: Write Protect is on
sdc: assuming drive cache: write through
SCSI device sdc: 1024 512-byte hdwr sectors (1 MB)
sdc: Write Protect is on
sdc: assuming drive cache: write through
sdc:7usb-storage: queuecommand called
sdc1 sdc4
See there are 2 partitions detected: sdc1 sdc4. SO try mounting these.
sd 1:0:0:1: Attached scsi disk sdc
sd 1:0:0:1: Attached scsi generic sg2 type 0
[snip]
I mounted usbfs and able to see mass storage in /proc/bus/usb/devices
However when I try to mount by
Mount -t vfat /dev/sda /mnt/pendrive then
^^^
replace `sda` with `sdc1` or `sdc4` in the mount command above.
From the above messages you see only 'sdb' 'sdc', plus 'sdb' has no
vaild partition table! So you are left with 'sdc'.
I get error Mounting /dev/sda on /mems failed: No such device
I tried it on sdb and sdc as well but it's not mounted.
Can any one tell me abt possible problem?
Regards
Manish
Hope this helps!
Thanks,
Subhash
-
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 Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
-
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 Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
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] [PATCH 2.6.17-rc5] USB OHCI DRIVER: ohci-hcd.c doesn't compile as module when USB_OHCI_HCD_PPC_SOC and PCI are set
-#if !(defined(CONFIG_PCI) \ - || defined(CONFIG_SA) \ - || defined(CONFIG_ARCH_S3C2410) \ - || defined(CONFIG_ARCH_OMAP) \ - || defined (CONFIG_ARCH_LH7A404) \ - || defined (CONFIG_PXA27x) \ - || defined (CONFIG_SOC_AU1X00) \ - || defined (CONFIG_USB_OHCI_HCD_PPC_SOC) \ - || defined (CONFIG_ARCH_AT91RM9200) \ - ) +#if !defined(PCI_DRIVER) !defined(SA_DRIVER) typo in the above line, I think it's to be PLATFORM_DRIVER not SA_DRIVER ! #error missing bus glue for ohci-hcd #endif Thanks, Subhash --- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642 ___ 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] EHCI Host not enumerating device
Hi subhash, What was the PHY Chip u have used. My PHY Chip is SMSC USB3300 , which has an reset pin, but is not connected to any pin, but is left as an input, We are trying to find it out. Thanks for ur timely help. Did u come across the same problem of not getting interrupts when u connect a device to the OTG port. But u were able to solve it, when u did a PHY reset, But how did u do the reset... was it software or a separate pin on the board. In my case, GPIO pin from the main board drives the reset pin. Are you using GPIO? Have you verified your main board PCB layout (_not_ ARC controller)? Usually the main board provides set of GPIO registers, so you need to set the approproate bit in one of those registers to drive that pin. If it is a software reset, then can u tell me in whcich register did u do that in the ARC Controller, if the PHY register set was not directly accessible. For me the PHY register set is not directly accessible. It has _nothing_ to do with ARC controller, which doesn't provide any way to access PHY registers. When I mentioned check your spec sheet, I'm talking about your _main_ _chip_ that controls entire system, _not_ about ARC controller. Please tell me , what other problems , u had to face, since that would help us in a great deal. Thanks very much rak Thanks, Subhash On 5/22/06, Subhash Reddy Peddamallu [EMAIL PROTECTED] wrote: Hi Subhash, Thanks for ur comments, My PHY chip is SMSC USB3300 chip which is ULPI Compliant, I have gone through the pin diagram of this Chip, There is a pin - 9 in this chip which is the RESET pin for this chip, But i dont see any external reset button facility for this purpose. I was looking for a GPIO pin which when set,would drive the PHY reset, But i was not able to find one in the ARC Controller doc. I don't think you find this info in ARC controller doc, but check your main board spec sheet (and also check PCB sheet where this PHY chip is placed) to know the procedure to drive reset pin, also it will give an idea of what you really need to do. All this are really specific to your system so without knowing board spec sheet, I can't say much. I have a ULPI View port register, which provides indirect access to the ULPI PHY register set. So this one is the register i was looking for. But i ignored it earlier, since it says writes to this register are not guaranteed, not to affect USB Transfers. The ULPI View port register has no bit for ULPI Reset, But bit-31 is for ULPI Wakeup. If u have used ARC, and was ur PHY SMSC 3300 , if it is , please provide information on how to reset. I'm not familiar with PHY SMSC 3300 chip! Also, which device have u used to connect to the OTG port. Thanks Rakesh Thanks, Subhash On 5/19/06, Subhash Reddy Peddamallu [EMAIL PROTECTED] wrote: Hi Rakesh, Hi Subash, I am using ARC HS-OTG Core with ULPI Interface. Hope the ARC PHY u are referring to is this ULPI interface. That means you do have ULPI tranceiver chip, that actually provides USB PHY interface. BTW, it's not ARC PHY here. My kernel is 2.6.16-11, the thing is that in device controller mode , we are receiving interrupts. Can u provide some information on the following:- 1) What is the device u have used to plug in to the ARC. Since the ARC HS Core is OTG in our case, we cannot connect a device with power requirements of more that 8mA, and it should be self powered also. I don't get your question! Are you asking, which device I plugged in to the USB port? 2) We have in our docs , only one to reset , that is the ARC Controller Core. If the controller u used has an ULPI interface, can u tell me how did u reset the PHY. I think you need to reset ULPI tranceiver chip. Check your ULPI tranceiver chip data sheet to make sure whether you need to reset. (usually in pin diagram, look for external reset pin). If there is reset pin, then there should be a some GPIO pin from your main board that drives the ULPI reset pin. One more thing, see pins that connect your main board ULPI chip are configured correctly. I mean, in some cases those pins are dual-role pins so you need to configure them for USB operation. Most of the stuff is platform specific, so I can't say where the problem is. 3) The thing is the root hub is getting recognized correctly, that means the controller has been properly initialised is what i think. Correct me if i am wrong. See cat /proc/interrupts to make sure you are getting interrupts in normal device mode. Also post cat /proc/bus/usb/devices before after plugging in a device into USB port. Please help me with ur comments, since u have already worked on this. Thanks Rak Subhash PS: cc'ing to linux-usb-devel@lists.sourceforge.net, so
Re: [linux-usb-devel] EHCI Host not enumerating device
Hi Subhash, Thanks for ur comments, My PHY chip is SMSC USB3300 chip which is ULPI Compliant, I have gone through the pin diagram of this Chip, There is a pin - 9 in this chip which is the RESET pin for this chip, But i dont see any external reset button facility for this purpose. I was looking for a GPIO pin which when set,would drive the PHY reset, But i was not able to find one in the ARC Controller doc. I don't think you find this info in ARC controller doc, but check your main board spec sheet (and also check PCB sheet where this PHY chip is placed) to know the procedure to drive reset pin, also it will give an idea of what you really need to do. All this are really specific to your system so without knowing board spec sheet, I can't say much. I have a ULPI View port register, which provides indirect access to the ULPI PHY register set. So this one is the register i was looking for. But i ignored it earlier, since it says writes to this register are not guaranteed, not to affect USB Transfers. The ULPI View port register has no bit for ULPI Reset, But bit-31 is for ULPI Wakeup. If u have used ARC, and was ur PHY SMSC 3300 , if it is , please provide information on how to reset. I'm not familiar with PHY SMSC 3300 chip! Also, which device have u used to connect to the OTG port. Thanks Rakesh Thanks, Subhash On 5/19/06, Subhash Reddy Peddamallu [EMAIL PROTECTED] wrote: Hi Rakesh, Hi Subash, I am using ARC HS-OTG Core with ULPI Interface. Hope the ARC PHY u are referring to is this ULPI interface. That means you do have ULPI tranceiver chip, that actually provides USB PHY interface. BTW, it's not ARC PHY here. My kernel is 2.6.16-11, the thing is that in device controller mode , we are receiving interrupts. Can u provide some information on the following:- 1) What is the device u have used to plug in to the ARC. Since the ARC HS Core is OTG in our case, we cannot connect a device with power requirements of more that 8mA, and it should be self powered also. I don't get your question! Are you asking, which device I plugged in to the USB port? 2) We have in our docs , only one to reset , that is the ARC Controller Core. If the controller u used has an ULPI interface, can u tell me how did u reset the PHY. I think you need to reset ULPI tranceiver chip. Check your ULPI tranceiver chip data sheet to make sure whether you need to reset. (usually in pin diagram, look for external reset pin). If there is reset pin, then there should be a some GPIO pin from your main board that drives the ULPI reset pin. One more thing, see pins that connect your main board ULPI chip are configured correctly. I mean, in some cases those pins are dual-role pins so you need to configure them for USB operation. Most of the stuff is platform specific, so I can't say where the problem is. 3) The thing is the root hub is getting recognized correctly, that means the controller has been properly initialised is what i think. Correct me if i am wrong. See cat /proc/interrupts to make sure you are getting interrupts in normal device mode. Also post cat /proc/bus/usb/devices before after plugging in a device into USB port. Please help me with ur comments, since u have already worked on this. Thanks Rak Subhash PS: cc'ing to linux-usb-devel@lists.sourceforge.net, so that other developers can correct us when we go wrong. On 5/19/06, Subhash Reddy Peddamallu [EMAIL PROTECTED] wrote: Hi all, We are testing EHCI driver for ARC based controller core on a ARM 926 board. The platform glue has been written. The driver is compiled to the kernel . When the kernel boots up , the driver is loaded. I used the similar setup, ARC EHCI core with ARM borad. I implemented bus glue, but in 2.4, its working fine. We have enabled USB_DEBUG and then going through the prints, its is observed that the root hub has been identified and given the address 1. Are you sure EHCI controller started correctly? Check cat /proc/bus/usb/devices if you have usbfs. But when we plug a High Speed device , the IRQ function is not even invoked, the STS register and PCD bit in PORTSCx is not showing any change. See cat /proc/interrupts to make sure you really getting interrupts, i.e see before plugging any device after plugging a device. Those who have worked with ARC USB HS-OTG controllers, have u come across these problems, if yes, please help us. I faced the similar problem- with this setup (i.e ARC core on ARM board), at init time you may need to reset USB PHY, probably through GPIO pin or ?? This is just my guess, in my case I forgot to do this it took hours to figure out this. Check with your data sheet make sure you are not seeing this problem. I have no other ideas for what might be causing the problem, if you can post
Re: [linux-usb-devel] EHCI Host not enumerating device
Hi Rakesh, Hi Subash, I am using ARC HS-OTG Core with ULPI Interface. Hope the ARC PHY u are referring to is this ULPI interface. That means you do have ULPI tranceiver chip, that actually provides USB PHY interface. BTW, it's not ARC PHY here. My kernel is 2.6.16-11, the thing is that in device controller mode , we are receiving interrupts. Can u provide some information on the following:- 1) What is the device u have used to plug in to the ARC. Since the ARC HS Core is OTG in our case, we cannot connect a device with power requirements of more that 8mA, and it should be self powered also. I don't get your question! Are you asking, which device I plugged in to the USB port? 2) We have in our docs , only one to reset , that is the ARC Controller Core. If the controller u used has an ULPI interface, can u tell me how did u reset the PHY. I think you need to reset ULPI tranceiver chip. Check your ULPI tranceiver chip data sheet to make sure whether you need to reset. (usually in pin diagram, look for external reset pin). If there is reset pin, then there should be a some GPIO pin from your main board that drives the ULPI reset pin. One more thing, see pins that connect your main board ULPI chip are configured correctly. I mean, in some cases those pins are dual-role pins so you need to configure them for USB operation. Most of the stuff is platform specific, so I can't say where the problem is. 3) The thing is the root hub is getting recognized correctly, that means the controller has been properly initialised is what i think. Correct me if i am wrong. See cat /proc/interrupts to make sure you are getting interrupts in normal device mode. Also post cat /proc/bus/usb/devices before after plugging in a device into USB port. Please help me with ur comments, since u have already worked on this. Thanks Rak Subhash PS: cc'ing to linux-usb-devel@lists.sourceforge.net, so that other developers can correct us when we go wrong. On 5/19/06, Subhash Reddy Peddamallu [EMAIL PROTECTED] wrote: Hi all, We are testing EHCI driver for ARC based controller core on a ARM 926 board. The platform glue has been written. The driver is compiled to the kernel . When the kernel boots up , the driver is loaded. I used the similar setup, ARC EHCI core with ARM borad. I implemented bus glue, but in 2.4, its working fine. We have enabled USB_DEBUG and then going through the prints, its is observed that the root hub has been identified and given the address 1. Are you sure EHCI controller started correctly? Check cat /proc/bus/usb/devices if you have usbfs. But when we plug a High Speed device , the IRQ function is not even invoked, the STS register and PCD bit in PORTSCx is not showing any change. See cat /proc/interrupts to make sure you really getting interrupts, i.e see before plugging any device after plugging a device. Those who have worked with ARC USB HS-OTG controllers, have u come across these problems, if yes, please help us. I faced the similar problem- with this setup (i.e ARC core on ARM board), at init time you may need to reset USB PHY, probably through GPIO pin or ?? This is just my guess, in my case I forgot to do this it took hours to figure out this. Check with your data sheet make sure you are not seeing this problem. I have no other ideas for what might be causing the problem, if you can post your bus glue code. I am attaching the log of trace i did. It's really difficult to understand this log with your printk's, better if you takeout your own printk's its enough to have USB_DEBUG enabled. Thanks Rak Hope this helps! Subhash Function register_root_hub is called ,root hub device address = 1 issuing get_descriptor in register_root_hub Function usb_get_device_descriptor called Function usb_get_descriptor called Function usb_submit_urb called Function hcd_submit_urb is called Calling function rh_urb_enqueue to queue Setup URB to Root Hub Function rh_call_control called...This ultimately calls hc_driver-hub_control rh_call_control URB setup_packet contents in rh_call_control typeReq = 8006, wValue = 100, wIndex = 0, wLength = 12 Issued usb_control_msg request. result = 18 Function usb_get_descriptor Returned leaving function usb_get_device_descriptor Length of received desc is 0x12 12 1 0 2 9 0 1 40 0 0 0 0 6 2 3 2 1 1 Function usb_new_device called Function usb_get_configuration called for root-hub No of configurations for root-hub = 1 Function usb_get_descriptor called Function usb_submit_urb called Function hcd_submit_urb is called Calling function rh_urb_enqueue to queue Setup URB to Root Hub Function rh_call_control called...This ultimately calls hc_driver-hub_control rh_call_control URB setup_packet contents in rh_call_control typeReq = 8006, wValue = 200, wIndex = 0
Re: [linux-usb-devel] EHCI Host not enumerating device
Hi all, We are testing EHCI driver for ARC based controller core on a ARM 926 board. The platform glue has been written. The driver is compiled to the kernel . When the kernel boots up , the driver is loaded. I used the similar setup, ARC EHCI core with ARM borad. I implemented bus glue, but in 2.4, its working fine. We have enabled USB_DEBUG and then going through the prints, its is observed that the root hub has been identified and given the address 1. Are you sure EHCI controller started correctly? Check cat /proc/bus/usb/devices if you have usbfs. But when we plug a High Speed device , the IRQ function is not even invoked, the STS register and PCD bit in PORTSCx is not showing any change. See cat /proc/interrupts to make sure you really getting interrupts, i.e see before plugging any device after plugging a device. Those who have worked with ARC USB HS-OTG controllers, have u come across these problems, if yes, please help us. I faced the similar problem- with this setup (i.e ARC core on ARM board), at init time you may need to reset USB PHY, probably through GPIO pin or ?? This is just my guess, in my case I forgot to do this it took hours to figure out this. Check with your data sheet make sure you are not seeing this problem. I have no other ideas for what might be causing the problem, if you can post your bus glue code. I am attaching the log of trace i did. It's really difficult to understand this log with your printk's, better if you takeout your own printk's its enough to have USB_DEBUG enabled. Thanks Rak Hope this helps! Subhash Function register_root_hub is called ,root hub device address = 1 issuing get_descriptor in register_root_hub Function usb_get_device_descriptor called Function usb_get_descriptor called Function usb_submit_urb called Function hcd_submit_urb is called Calling function rh_urb_enqueue to queue Setup URB to Root Hub Function rh_call_control called...This ultimately calls hc_driver-hub_control rh_call_control URB setup_packet contents in rh_call_control typeReq = 8006, wValue = 100, wIndex = 0, wLength = 12 Issued usb_control_msg request. result = 18 Function usb_get_descriptor Returned leaving function usb_get_device_descriptor Length of received desc is 0x12 12 1 0 2 9 0 1 40 0 0 0 0 6 2 3 2 1 1 Function usb_new_device called Function usb_get_configuration called for root-hub No of configurations for root-hub = 1 Function usb_get_descriptor called Function usb_submit_urb called Function hcd_submit_urb is called Calling function rh_urb_enqueue to queue Setup URB to Root Hub Function rh_call_control called...This ultimately calls hc_driver-hub_control rh_call_control URB setup_packet contents in rh_call_control typeReq = 8006, wValue = 200, wIndex = 0, wLength = 9 Issued usb_control_msg request. result = 9 Function usb_get_descriptor Returned Function usb_get_descriptor called Function usb_submit_urb called Function hcd_submit_urb is called Calling function rh_urb_enqueue to queue Setup URB to Root Hub Function rh_call_control called...This ultimately calls hc_driver-hub_control rh_call_control URB setup_packet contents in rh_call_control typeReq = 8006, wValue = 200, wIndex = 0, wLength = 19 Issued usb_control_msg request. result = 25 Function usb_get_descriptor Returned Returned from function usb_get_configuration Function usb_submit_urb called Function hcd_submit_urb is called Calling function rh_urb_enqueue to queue Setup URB to Root Hub Function rh_call_control called...This ultimately calls hc_driver-hub_control rh_call_control URB setup_packet contents in rh_call_control typeReq = 8006, wValue = 300, wIndex = 0, wLength = ff usb usb1: default language 0x0409 Function usb_submit_urb called Function hcd_submit_urb is called Calling function rh_urb_enqueue to queue Setup URB to Root Hub Function rh_call_control called...This ultimately calls hc_driver-hub_control rh_call_control URB setup_packet contents in rh_call_control typeReq = 8006, wValue = 302, wIndex = 409, wLength = ff Function usb_submit_urb called Function hcd_submit_urb is called Calling function rh_urb_enqueue to queue Setup URB to Root Hub Function rh_call_control called...This ultimately calls hc_driver-hub_control rh_call_control URB setup_packet contents in rh_call_control typeReq = 8006, wValue = 303, wIndex = 409, wLength = ff Function usb_submit_urb called Function hcd_submit_urb is called Calling function rh_urb_enqueue to queue Setup URB to Root Hub Function rh_call_control called...This ultimately calls hc_driver-hub_control rh_call_control URB setup_packet contents in rh_call_control typeReq = 8006, wValue = 301, wIndex = 409, wLength = ff usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EHCI Host Controller usb usb1: Manufacturer: Linux 2.6.16.11 ehci_hcd usb usb1:
Re: [linux-usb-devel] usb-storage debugging
On 1/20/06, Alan Stern [EMAIL PROTECTED] wrote: What do you get from dd if=/dev/sda count=1 | hexdump -C? Alan Stern Hi, % dd if=/dev/sda count=1 | hexdump gives all zeroes. If I increase count, occasionally some data shows up which isn't meaningful ascii, but mostly zero. The same flashdisk mounts fine on a known-to-work platform, and shows the same output for the above command. Also below is what I get from usb-storage when I type the above command on the platform that fails mounting. Do you have a suggestion for what to check? Since the drive mounts fine on a host controller that works, I guess it's not the partition table I need to inspect? Make sure you enabled config option (e.g MAC_PARTITION or MSDOS_PARTITION etc) for right partition type support when you compile kernel. For e.g. if you seen the disk working on windows, then enable support for MSDOS_PARTITION. Give it a try, this might fix the problem. Many thanks, Bahadir Subhash --- 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://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ 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] Help
Hello Conio, Hello Alan, Please review the following error messages that i am getting - and I am not able to mount the usb pendrive , I have a EXT2 root file system and the usb pendrive has a VFAT file system Make sure you enabled right partition type under Config options, try enabling the PC-BIOS partition type (I think thats the most common one). Hope that helps! Subhash --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ 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] usbcore issue in 2.4.25 or later kernels
Hello Pete,
Can you please look at this issue?
This is just an workaround for few flaky devices.
Let me know your comments.
Thanks,
Subhash
Hello all,
I'm using 2.4.25 kernel and I got following error messages when I plugged
in Linksys USB Network adaptor or NewMedia USB modem. (mass storage
devices work fine.)
usb.c: not enough configurations
usb.c: unable to get device 2 configuration (error=-22)
So to solve this problem I was modifying usb.c and I came across the
following code in the function usb_get_descriptor,
while (i--) {
if ((result = usb_control_msg(dev, usb_rcvctrlpipe(dev, 0),
USB_REQ_GET_DESCRIPTOR, USB_DIR_IN,
(type 8) + index, 0, buf, size, HZ * GET_TIMEOUT)) 0
||
result == -EPIPE)
break; /* retry if the returned length was 0; flaky device
*/
}
I think we do not want to break from the loop when result == -EPIPE, we
just want to continue. Also I think we have to make sure its not giving
descriptor with zero values (the reason for this, when I printed the
descriptor values, it has zero for all its fields. This is not what we
want). Can anybody please explain why this happens?
I just added these checks (actually I stolen these checks from 2.6
kernel). It now works fine!!
If anybody is having the same problem , try this modified code (inside
while loop). This may fix the problem! I'm not sure.
result = usb_control_msg(dev, usb_rcvctrlpipe(dev, 0),
USB_REQ_GET_DESCRIPTOR, USB_DIR_IN,
(type 8) + index, 0, buf, size, HZ *
USB_CTRL_GET_TIMEOUT); if (result == 0 || result ==
-EPIPE)
continue;
if (result 1 ((u8 *)buf)[1] != type) {
result = -EPROTO;
continue;
}
I found the same problem with 2.4.31 kernel, don't know about 2.4.32.
Any comments?
Subhash
---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
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:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
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] usbcore issue in 2.4.25 or later kernels
Hello all,
I'm using 2.4.25 kernel and I got following error messages when I plugged
in Linksys USB Network adaptor or NewMedia USB modem. (mass storage
devices work fine.)
usb.c: not enough configurations
usb.c: unable to get device 2 configuration (error=-22)
So to solve this problem I was modifying usb.c and I came across the
following code in the function usb_get_descriptor,
while (i--) {
if ((result = usb_control_msg(dev, usb_rcvctrlpipe(dev, 0),
USB_REQ_GET_DESCRIPTOR, USB_DIR_IN,
(type 8) + index, 0, buf, size, HZ * GET_TIMEOUT)) 0 ||
result == -EPIPE)
break; /* retry if the returned length was 0; flaky device */
}
I think we do not want to break from the loop when result == -EPIPE, we
just want to continue. Also I think we have to make sure its not giving
descriptor with zero values (the reason for this, when I printed the
descriptor values, it has zero for all its fields. This is not what we
want). Can anybody please explain why this happens?
I just added these checks (actually I stolen these checks from 2.6
kernel). It now works fine!!
If anybody is having the same problem , try this modified code (inside
while loop). This may fix the problem! I'm not sure.
result = usb_control_msg(dev, usb_rcvctrlpipe(dev, 0),
USB_REQ_GET_DESCRIPTOR, USB_DIR_IN,
(type 8) + index, 0, buf, size, HZ *
USB_CTRL_GET_TIMEOUT); if (result == 0 || result ==
-EPIPE)
continue;
if (result 1 ((u8 *)buf)[1] != type) {
result = -EPROTO;
continue;
}
I found the same problem with 2.4.31 kernel, don't know about 2.4.32.
Any comments?
Subhash
---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
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] Philips ISP1761 support
Hi Sanjay, Hi All, I am new to this mailing list and also new to Linux USB host drivers. In one of the project we are using Philips ISP1761 USB host controller (memory mapped). It has 2 host ports and one OTG port. As per documentation, it is supposed to be EHCI compliant. Question: does linux has built in EHCI support for non-PCI EHCI controllers AFAIK, there is no support for non-pci EHCI controllers. But you can add that support, its not that difficult (just few weeks back I did for ARC's non-pci controller). See non-pci OHCI controllers: ohci-lh7a404.c, etc... Check some David Brown's previous mails on this topic. , also having OTG? has any one trird using ISP1761 or ISP1760? Thanks, sanjay Good luck, Subhash --- 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] USB driver binding
Hi! I am writing a bulk transfer driver for data xfer through host-to-host xfer cable. I don't want to use the usbnet driver for the same. This driver is based on usb-skeleton.c and presently tested with PL-2301 chips. My problem is that I want the driver binding to happen for all such kind of cable from different vendors and from new vendors also in future. I think you can use Device class subclass instead of Vendor id/device id. How can I create a little more generic usb_device_id entry rather than very specifically mentioning the VendorID and device ID of all such cables from different manufacturers. Do all these cables fall under a particulas combination of device class and subclass? Yes, they fall under USB communication class. As an example see usb/acm.c. For more info on this, see the comments in usb.c before function usb_match_id. Lets see what usb experts say. Alternatively is there any way where I can set come configuration mentioning vendor ID and device ID and and corresponding module name, so that the module gets binded with devices from this particular combination of vendor and device ID. Again, see usb/acm.c Subhash --- 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] USB driver binding
My problem is that I want the driver binding to happen for all such kind of cable from different vendors and from new vendors also in future. I think you can use Device class subclass instead of Vendor id/device id. That assumes there IS a class. (And that those cost-cutting vendors implement it correctly ...) But I've yet to see such cables implement any communications device class spec; IMO there's likely no better solution than maintaining a list of vendor and product codes. Thats right, but he wants to support new (future) vendors! How can I create a little more generic usb_device_id entry rather than very specifically mentioning the VendorID and device ID of all such cables from different manufacturers. Do all these cables fall under a particulas combination of device class and subclass? Yes, they fall under USB communication class. As an example see usb/acm.c. Actually, don't. That's a 2.4 file. Use 2.6 kernels. :) Don't they fall under Communication class? I thought so, if not please correct me. That's 2.4 file, sorry. Please check 2.6 file: usb/class/cdc-acm.c And by the way, if the device implements such a class, you should use the standard Linux-USB driver for that class unless you are planning to replace that driver. - Dave For more info on this, see the comments in usb.c before function usb_match_id. --- 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] cat /proc/bus/usb/devices not showing all the devices info
Hello all, I recently implemented a platform bus glue for on-chip EHCI host controller (ARCs EHCI) which has roothub with built in TT. This uses most of the existing EHCI driver code. When I built kernel with this driver included, it loads without any major problems (please see the /proc/kmsg below). 4CPU: Arm920Tid(wb) revision 0 4Security risk: creating user accessible mapping for 0xf000 at 0xf000 4Security risk: creating user accessible mapping for 0xf000 at 0xf800 4On node 0 totalpages: 8192 4zone(0): 8192 pages. 4zone(1): 0 pages. 4zone(2): 0 pages. 4Kernel command line: root=/dev/ram mem=32M 7Relocating machine vectors to 0x 4Calibrating delay loop... 89.70 BogoMIPS 6Memory: 32MB = 32MB total 5Memory: 18144KB available (1431K code, 452K data, 60K init) 6Dentry cache hash table entries: 4096 (order: 3, 32768 bytes) 6Inode cache hash table entries: 2048 (order: 2, 16384 bytes) 6Mount cache hash table entries: 512 (order: 0, 4096 bytes) 6Buffer cache hash table entries: 1024 (order: 0, 4096 bytes) 4Page-cache hash table entries: 8192 (order: 3, 32768 bytes) 6CPU: Testing write buffer: pass 4POSIX conformance testing by UNIFIX 6PCI: bus0: Fast back to back transfers disabled 6Linux NET4.0 for Linux 2.4 6Based upon Swansea University Computer Society NET3.039 4Initializing RT netlink socket 4Starting kswapd 6devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) 6devfs: devfs_debug: 0x0 6devfs: boot_options: 0x1 6i2c-core.o: i2c core module version 2.6.1 (20010830) 6i2c-dev.o: i2c /dev entries driver module version 2.6.1 (20010830) 4ttyRI%d0 at MMIO 0xe0412000 (irq = 2) is a CNXTUART 4pty: 256 Unix98 ptys configured 4RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize 6loop: loaded (max 8 devices) 68139too Fast Ethernet driver 0.9.26 6eth0: RealTek RTL8139 at 0x4280, 00:40:f4:33:7b:8c, IRQ 37 7eth0: Identified 8139 chip type 'RTL-8139C' 6SCSI subsystem driver Revision: 1.00 6scsi0 : scsi_debug, Version: 0.61 (20020815), num_devs=1, dev_size_mb=8, opts=0x0 4 Vendor: Linux Model: scsi_debugRev: 0004 4 Type: Direct-Access ANSI SCSI revision: 03 4Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 4SCSI device sda: 16384 512-byte hdwr sectors (8 MB) 6Partition check: 6 /dev/scsi/host0/bus0/target0/lun0: unknown partition table 6usb.c: registered new driver usbdevfs 6usb.c: registered new driver hub 6usb.c: new USB bus registered, assigned bus number 1 7ehci_hcd NULL: ehci_start hcs_params 0x10011 dbg=0 ind cc=0 pcc=0 ordered ports=1 7ehci_hcd NULL: ehci_start hcc_params 0006 thresh 0 uframes 256/512/1024 park 7ehci_hcd NULL: reset command 080b02 park=3 ithresh=8 period=1024 Reset HALT 7ehci_hcd NULL: reset command 080b02 park=3 ithresh=8 period=1024 Reset HALT 7ehci_hcd NULL: init command 010b09 park=3 ithresh=1 period=256 RUN 6ehci_hcd NULL: USB enabled, EHCI 1.00, driver 2003-Dec-29/2.4 7hcd.c: hsx root hub device address 1 7usb.c: kmalloc IF 400139c0, numif 1 7usb.c: new device strings: Mfr=3, Product=2, SerialNumber=1 7usb.c: USB device number 1 default language ID 0x0 6Manufacturer: Linux 2.4.25-vrs1-cnxt ehci_hcd 6Product: ARCs EHCI 6SerialNumber: hsx 6hub.c: USB hub found 6hub.c: 1 port detected 7hub.c: standalone hub 7hub.c: individual port power switching 7hub.c: individual port over-current protection 7hub.c: Single TT 7hub.c: TT requires at most 8 FS bit times 7hub.c: Port indicators are supported 7hub.c: power on to power good time: 0ms 7hub.c: hub controller current requirement: 0mA 7hub.c: port removable status: R 7hub.c: local power source is good 7hub.c: no over-current condition exists 7hub.c: enabling power on all ports 7usb.c: hub driver claimed interface 400139c0 7usb.c: kusbd: /sbin/hotplug add 1 7usb.c: kusbd policy returned 0xfffe 6usb.c: registered new driver hiddev 6usb.c: registered new driver hid 6hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik [EMAIL PROTECTED] 6hid-core.c: USB HID support drivers 6Initializing USB Mass Storage driver... 6usb.c: registered new driver usb-storage 6USB Mass Storage support registered. 6NET4: Linux TCP/IP 1.0 for NET4.0 6IP Protocols: ICMP, UDP, TCP 6IP: routing cache hash table of 512 buckets, 4Kbytes 6TCP: Hash tables configured (established 2048 bind 4096) 6NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 4Fast Floating Point Emulator V0.9 (c) Peter Teichmann. 5RAMDISK: ext2 filesystem found at block 0 5RAMDISK: Loading 8192 blocks [1 disk] into ram disk... done. 6Freeing initrd memory: 12288K 7ehci_hcd NULL: GetStatus port 1 status 001403 POWER sig=k CSC CONNECT 7hub.c: port 1, portstatus 101, change 1, 12 Mb/s 7hub.c: port 1 connection change 7hub.c: port 1, portstatus 101, change 1, 12 Mb/s 4VFS: Mounted root (ext2 filesystem) readonly. 6Mounted devfs on /dev 6Freeing init memory: 60K 7hub.c: port 1, portstatus 101, change 0, 12 Mb/s 7hub.c: port 1, portstatus 101, change 0, 12 Mb/s 7hub.c: port 1, portstatus 101, change 0, 12 Mb/s 7hub.c:
Re: [linux-usb-devel] on-chip EHCI controller
Hello, Can anybody please help me on writing the EHCI driver for platform specific bus (non-PCI)? Please let me know are there any examples for non-PCI EHCI. If you need more info please let me know. Thanks, Subhash Hello All, I'm using ARC's EHCI host controller and so I used Craig Nadler's patch. But its not recognizing the host controller. Later I found that its an on-chip host controller (i.e non-PCI). How to add support for on-chip controllers? Can anybody help me how to proceed from this situation? Are there any support for such controllers already? I'm using 2.4.25 kernel running on a processor based on ARM920T core. (I understand you guys encourage using 2.6 kernel, but I have to work on 2.4 for now.) Thanks, Subhash --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ 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] on-chip EHCI controller
At 10:24 AM 8/10/2005 -0400, you wrote: Hello, Can anybody please help me on writing the EHCI driver for platform specific bus (non-PCI)? Please let me know are there any examples for non-PCI EHCI. If you need more info please let me know. Thanks, Subhash Hello All, I'm using ARC's EHCI host controller and so I used Craig Nadler's patch. But its not recognizing the host controller. Later I found that its an on-chip host controller (i.e non-PCI). How to add support for on-chip controllers? Can anybody help me how to proceed from this situation? Are there any support for such controllers already? I'm using 2.4.25 kernel running on a processor based on ARM920T core. (I understand you guys encourage using 2.6 kernel, but I have to work on 2.4 for now.) Thanks, Subhash Hi Subhash, I did the same thing on a FreeBSD system using the arc core. The problem is the details of your local bus will be extremely specific to your platform, ASIC/FPGA core, and processor. This is not an issue for linux-usb-devel, there is no way anyone can help when you are using an ancient kernel interfacing via an unknown bus to your custom hardware. What you have to do is UTSL and look at a comparable driver and how it tied into the bus, for instance if you have an onchip ethernet mac/phy and it is controlled by a kernel driver you can try and duplicate how THAT driver hooks into the local buses and do likewise. There is no easy, packaged way over this hurdle. Regards ~Steve Thanks Steve. I will go through the sources. Can you please tell me the things I need to know about the bus to write a driver. The reason I'm asking is: we are using HSX bus and I don't know nothing about it. When I googled it, I didn't find any useful info. If you know about HSX bus, can you please tell me about it. Thanks a lot, Subhash --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ 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] on-chip EHCI controller
Hello All, I'm using ARC's EHCI host controller and so I used Craig Nadler's patch. But its not recognizing the host controller. Later I found that its an on-chip host controller (i.e non-PCI). How to add support for on-chip controllers? Can anybody help me how to proceed from this situation? Are there any support for such controllers already? I'm using 2.4.25 kernel running on a processor based on ARM920T core. (I understand you guys encourage using 2.6 kernel, but I have to work on 2.4 for now.) Thanks, Subhash --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ 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] Re: EHCI controller with a built in TT
Hi Craig, Thanks for the patch. I will apply your patch now and see how it goes. For now I'm using 2.4.25 (and will continue for sometime), however in future I will move to 2.6 series. Thanks, Subhash Hi Subhash, I've attached a patch for the Linux 2.4.26 kernel that adds root hub TT support. Please keep in mind that this patch is unsupported, I would encourage you to upgrade to Linux 2.6.10 or later. The maintainer for the Linux 2.4 kernel opted not to include this patch in the 2.4 branch so 2.4 kernels will need to be patched manually. Best Regards, Craig Nadler TransDimension Inc. Original message Date: Tue, 2 Aug 2005 12:28:41 -0400 (EDT) From: [EMAIL PROTECTED] Subject: EHCI controller with a built in TT To: linux-usb-devel@lists.sourceforge.net Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Hello, I'm using ARC's EHCI controller which has a built in TT. I see this was supported in 2.6 kernel, but I'm working with 2.4.25 kernel. I'm wondering does anybody has patch for 2.4 which supports EHCI roothubs with a TT? If not, I would like to add this support to 2.4 Any suggestions or comments? Thanks, Subhash --- 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_id=7477alloc_id=16492op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
