Hi all,

I'm working on writing support for the USB HC available in our ST40GX1 system
on chip. This processor is basically a SH4 plus other devices (PCI, serial,
video, USB, Teletext and PWM) connected by an on-chip bus called SuperHyway.
The chip is mainly targeted at set-top-boxes and TV related applications.

On Linux all these devices are available as sections of the address space by
using the I/O functions readX()/writeX(). For example the standard OHCI
Operational Registers are available from kernel address 0xBB170000 after
setting some bits in a system-wide configuration register that controls these
on-chip devices.

Reading the usb-ohci.[ch] files is obvious that the OHCI controller (and
generally speaking all the HC's) is only expected to be found on the PCI bus.
To gain a better knowledge of the whole USB subsystem I'm trying to modify the
original code as little as possible (if it isn't broken, don't fix it :-) and
I'm only changing the pci related sections using conditional compilation. Some
of the features needed by a PCI implementation are not needed in our system
(e.g. hotplug) while extensive use of pci_* routines makes things more
difficult when it comes to memory management.

Has anyone already had the same problem? What about 2.5? IMHO some more
separation between OHCI code and bus code would help someone else: are there
other SOC's running Linux with the same problem? I'll look at the ARM chips
anyway.

Any help, idea or comment will be highly appreciated.
Thanks a lot.

-- 
------------------------------------------------------------
Mr. Andrea Cisternino             | Tel:  +44-(0)1454-462363
MCDT Division                     | TINA: 065 2363
STMicroelectronics Ltd.           | Fax:  +44-(0)1454-617910
1000 Aztec West, Almondsbury      |
Bristol BS32 4SQ                  | [EMAIL PROTECTED]
United Kingdom                    |

_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to