We (Motorola) have an integrated USB block that uses EHCI and are planning on putting it into embedded PPC (and other devices). I wanted to start a dialog to understand how we can modify the existing EHCI support to handle a non-PCI based access to the register space.
I suggest you look at how the "ohci-hcd" code does that. There are both OMAP and SA-1111 versions.
The short version of the story is that you'll need to split out the initialization into PCI bits (which most folk will use) and non-PCI bits (Motorola, and maybe a few others).
In our devices we have direct memory mapped access to the devices from the CPU. (goes over an internal hidden bus). Was wondering if anything already does this or if you have any comments about how to handle this.
The initialization code will just set up the memory-mapped I/O a bit differently than the PCI code. Given that, I don't think the main body of that driver will care much about PCI.
You might need to shuffle a few things around to make that work.
- Dave
Thanks
- Kumar
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
