Active Topics

 


Closed Thread
Thread Tools
MohammadAG's Avatar
Posts: 2,473 | Thanked: 12,265 times | Joined on Oct 2009 @ Jerusalem, PS/IL
#811
I don't have the slightest idea how this works, but Mer (based on Ubuntu 8.04) *should* have the drivers right? (correct me if I'm wrong).
Wouldn't switching to Mer allow the USB device to work (as in file transfers/mouse movement etc...)? (Just as a proof of concept)


Edit: scratch that, <Stskeeps> no, same kernel

Last edited by MohammadAG; 2010-05-09 at 19:38.
 
javispedro's Avatar
Posts: 2,355 | Thanked: 5,249 times | Joined on Jan 2009 @ Barcelona
#812
Originally Posted by egoshin View Post
I looked briefly in code - yes, there is no support for that kind of devices. But it should be supported via device class - hub at least for sure. So, some software debug print is needed to find out the whole info from device... tomorrow.
Hub device class driver is there for sure (root hub). A simple lsusb -v should print both the root hub and your external hub descriptors.
 

The Following User Says Thank You to javispedro For This Useful Post:
Posts: 306 | Thanked: 566 times | Joined on Jan 2010 @ Romania
#813
Originally Posted by egoshin View Post
OK, some success (at least I think so).

I used a wall-powered hub with USB memory stick and external USB hard drive. I applied 3.5V from TWL4030 to VBUS and set Host mode of operations in ARM CPU USB.

The result - in both cases a lot of communications (TX interrupts but no RX - ?) and finally the message -

Nokia-N900-42-11 kernel: [...] usb 1-1: device v04b4 p6560 is not supported <---- this is for USB Hub with USB memory stick

Nokia-N900-42-11 kernel: [...] usb 1-1: device v0bc2 p3000 is not supported <---- this is for USB hard disk.

EDIT: verified via SuSE notebook - Hard Disk is 0bc2:3000 Seagate RSS LLC, and HUB - 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub"

Taking into account the different Vendor (v*) and Product (p*) values and the very remarkable Product value for HDisk - p3000, I assume that it is values read from devices.


I looked briefly in code - yes, there is no support for that kind of devices. But it should be supported via device class - hub at least for sure. So, some software debug print is needed to find out the whole info from device... tomorrow.
your hub is well known usb.id
http://mxr.maemo.org/fremantle/sourc...ls/usb.ids#951
but hdd is not
AFIK usb devices attached to an otg or embedded host controller should be in a list named "Targeted Peripheral List"
http://mxr.maemo.org/fremantle/sourc...b/otg/otg.c#75

did you recognize this ?

164 /* OTG MESSAGE: report errors here, customize to match your product */
165 dev_err(&dev->dev, "device v%04x p%04x is not supported\n",
166 le16_to_cpu(dev->descriptor.idVendor),
167 le16_to_cpu(dev->descriptor.idProduct));
168
169 return 0;


you touch otg state machine

Last edited by blue_led; 2010-05-10 at 20:54.
 

The Following 4 Users Say Thank You to blue_led For This Useful Post:
Posts: 992 | Thanked: 995 times | Joined on Dec 2009 @ California
#814
Yes, I know this. But whitelist has this too:

83 /* hubs are optional in OTG, but very handy ... */
84 { USB_DEVICE_INFO(USB_CLASS_HUB, 0, 0), },
85 { USB_DEVICE_INFO(USB_CLASS_HUB, 0, 1), },

And hub should have USB HUB class in it's descriptor. Looks like something goes wrong in reading descriptor from device (it is worst case and it is strange - why does it read one descriptor but not other) but most probably - it is not debugged well in driver. It can be because HW still works as B-device but in HOST mode and driver knows this fact.

If so, I would like to use FORCE_HOST mode to switch in A-device state but who knows - it may be impossible without grounded ID pin and we should fix a driver.
 

The Following User Says Thank You to egoshin For This Useful Post:
Posts: 249 | Thanked: 167 times | Joined on Mar 2010 @ International
#815
At the risk of being on the wrong page,

doesnt this thread have any solutions?

http://talk.maemo.org/showthread.php?t=52227
__________________
How to ask questions the smart way
He who smiles in a crisis has found someone to blame.
Shirts get dirty. Underwear gets dirty. Pants? Pants never get dirty, and you can wear them forever.
My Favourite posts!
http://talk.maemo.org/showpost.php?p...&postcount=539
http://forums.precentral.net/2674180-post149.html
http://talk.maemo.org/showpost.php?p...&postcount=500
http://talk.maemo.org/showthread.php?t=63720
 
joerg_rw's Avatar
Posts: 2,222 | Thanked: 12,651 times | Joined on Mar 2010 @ SOL 3
#816
Originally Posted by egoshin View Post
It can be because HW still works as B-device but in HOST mode and driver knows this fact.

If so, I would like to use FORCE_HOST mode to switch in A-device state but who knows - it may be impossible without grounded ID pin and we should fix a driver.
No. The PHY chip and the musb in SoC obviously can talk to the hub, otherwise the vendor/product ids were not visible. I *honestly* doubt musb-hw on SoC has a problem like "I decide to cripple parts of data from device in HARDWARE because I'm in the wrong mode". In expression this is a SOFTWARE problem, not a hardware configuration issue.

And seriously - I thought we're thru with ID pin once and for all.

The above details show that driver is NOT in hostmode, but it still operates as a OTG device. We need to fix that - rather than any ID pin detection.

Last edited by joerg_rw; 2010-05-10 at 22:53.
 

The Following 5 Users Say Thank You to joerg_rw For This Useful Post:
Marshall Banana's Avatar
Posts: 94 | Thanked: 209 times | Joined on Oct 2009 @ Germany
#817
Originally Posted by gryedouge View Post
At the risk of being on the wrong page,

doesnt this thread have any solutions?

http://talk.maemo.org/showthread.php?t=52227
Actually the thread you linked is a synopsis of the results of this thread.

I think the thread "USB HOST MODE! (Coming soon)" was created to announce that usb host mode is (hopefully) comming soon for the n900. It's a place where the less tech-savvy people can inform themselves and discuss about usb host mode for the n900.

So talk about the BME, VBUS power, the TWL4030 and kernel patches goes here and talk about various devices to plug into the n900 and why nokia disabled it goes there.
 

The Following 5 Users Say Thank You to Marshall Banana For This Useful Post:
javispedro's Avatar
Posts: 2,355 | Thanked: 5,249 times | Joined on Jan 2009 @ Barcelona
#818
Ehm...

rx51_defconfig contains

CONFIG_USB_OTG_WHITELIST=y
CONFIG_USB_OTG_BLACKLIST_HUB=y

So why not disable them both?
 

The Following User Says Thank You to javispedro For This Useful Post:
Posts: 306 | Thanked: 566 times | Joined on Jan 2010 @ Romania
#819
i just landed on this too

i think we need whitelist but

1144 #ifdef CONFIG_USB_OTG_BLACKLIST_HUB
1145 if (hdev->parent) {
1146 dev_warn(&intf->dev, "ignoring external hub\n");
1147 return -ENODEV;
1148 }

and rx51_defconfig
1436 # CONFIG_USB_MUSB_HOST is not set
1437 # CONFIG_USB_MUSB_PERIPHERAL is not set
1438 CONFIG_USB_MUSB_OTG=y

so we have OTG only !!
memory behavior is provided by g_nokia and other modules ?

Last edited by blue_led; 2010-05-10 at 23:27.
 

The Following 2 Users Say Thank You to blue_led For This Useful Post:
joerg_rw's Avatar
Posts: 2,222 | Thanked: 12,651 times | Joined on Mar 2010 @ SOL 3
#820
Originally Posted by blue_led View Post
i just landed on this too

i think we need whitelist but

1144 #ifdef CONFIG_USB_OTG_BLACKLIST_HUB
1145 if (hdev->parent) {
1146 dev_warn(&intf->dev, "ignoring external hub\n");
1147 return -ENODEV;
1148 }

and rx51_defconfig
1436 # CONFIG_USB_MUSB_HOST is not set
1437 # CONFIG_USB_MUSB_PERIPHERAL is not set
1438 CONFIG_USB_MUSB_OTG=y

so we have OTG only !!
memory behavior is provided by g_nokia and other modules ?
well, we shouldn't need whitelist as it's a OTG thing. What we need though is a working hostmode triggered by 'echo host >mode'
printks from that whitelist thing indicate this hasn't been issued or it failed to take effect

so I absolutely agree on the CONFIG-*-* stuff needing further investigation. See one of my previous posts about suspicious/interesting things I stumbled over in rx51-defconfig

/jOERG
 

The Following 3 Users Say Thank You to joerg_rw For This Useful Post:
Closed Thread

Tags
awesomeness in the works, boulevard of broken deals, host, i am the dealbreaker, inspector gadget lies, mobidapter is a scam, nokia fanbois, otg, over 9000, usb, usbcontrol


 
Forum Jump


All times are GMT. The time now is 18:15.