Kyle Harris wrote:
Does it make sense to create an embedded (non-PCI) driver
based on the ohci or something else? It seems that, at least with the ezhost,
the controller differs from ohci considerably and the code must be modified
quite a bit. I'm hoping the experts can give me some direction.
If your current code is based on hc_simple, switch over to
use the "hcd" framework ... you'll be able to re-use more
of usbcore support, and it'll work better. Use "usbtest"
to test your HCD. It covers a lot of the main code paths,
including things I'm pretty sure hc_simple never handled.
I'd look at the (new!) ohci-lh7a404.c code mostly to see
how the bus glue can look using platform_device. And use
the rest of the OHCI driver to understand what the various
entries do ... it's probably the simplest HCD to understand.
But since your chip doesn't really resemble OHCI, there's
not a lot to re-use outside of usbcore. Nothing that
touches the chip registers would be reusable! And I don't
know that CY7C67300 chip at all; some of the models in the
OHCI code may not match it very well ... though if you put
firmware into the chip, you could probably provide the same
sort of work-queue/DMA model.
- Dave
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
