Well the API seems to still be moving as of 2.5.36 What is the 2nd argument of usb_register_root_hub supposed to be? I was reading the code and it shows it as the parent, but what is the meaning of a parent of a root hub? usb_register_root_hub appears to have been a replacement for the usb_new_device with this new parent arg. But as I was reading along I followed it back to SA1111_FAKE_PCIDEV for example which is nowhere else in the entire kernel tree (grep -r FAKE_PCI linux-2.5.36 -> only one reference in ohci) it seemed like it should be similar for user mode linux but I cant find any definitions for it. The other HCDs seem to trace back to a pci pointer where I lose track in the complexities of PCI and bus configuration.
Are there notes on how to build a HCD I have seen several sets on how to do a driver but since what I need to work on is a HCD they are less helpful. I think I understand how to relay the urbs and produce the fake hub but the various servcies registered and required seem to keep changing, some of which I can follow without too much trouble but others lose me. I suppose this is not to bad but I have to add ~5 patches just to get the linux code to compile on 2.5.36 and this recent usb change has lost me. It almost works but currently I have to manually return from a panic where submit_urb in the hcd derefences a null pointer the hcpriv field is 0, and since it was where the HCD data pointer is 0 is bad. It is acting like a urb is being submitted before the HCD init completes. It may even occur in the usb_register_root_hub :/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
