> I've been following this discussion for a while. I'm also working > on getting USB working on an isp1160 chip on a power pc platform. > Since I couldn't find any official drivers for this chip, I am > encouraged that there is some progress in this area.
Hey, I'm encouraged too. > I've got the driver compiling and I am able to read > basic registers on the device, but I don't think my driver gets > fully initialized. Mostly for curiosity: Is the driver reading the basic registers? What functions are you seeing this in? > * ohci_hcd_isp1362_init() doesn't do the actual HCD > initialization. That seems to happen in > ohci_hcd_isp1362_drv_probe(). uhoh. I haven't confirmed this, but according to Documentation/driver-model/driver.txt that should be in a init function. > However, in my system this function never seems to get called. I recently had the same trouble. I had defined a platform device, but changed the .name field. (which actually needed to match the driver's .name field.) > It gets assigned to the fn ptr ohci_hcd_isp1362_driver.probe, > which gets called in bus_probe, which gets assigned to driver.probe. > The device_driver driver gets registered in > hc_isp1362_driver_register. I don't know how device_driver.probe > gets called. What is the easiest way to to get this function called > properly? > I'm not familiar with how USB probes drivers and devices. If I were to guess, I think it's tied in with the platform_device registration (which you mentioned is different for 2.6.6). (OT: i didn't think this kinda stuff would change for a even-numbered kernel) > * When I was compiling the driver, I did not find any references to > include any of the provided header files in the isp1362 patch. > How did anyone get the driver to compile without these? Am I missing > something? > Which header files are you referring to? I didn't need much other than what came with the patch. Whatever I was missing, I think I found in include/asm-arm/arch-pxa/. > It seems there has been quite a bit of traffic on this thread over > the last > while. Would it make sense to have a separate mailing list for this > discussion? Not everyone else would be interested in these > developments. I would venture that it doesn't make much sense. There isn't that much traffic, and once it works for most people (or noone cares anymore) it'll die down. Plus, we'd still want feedback from all the other usb people. Mike ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
