-----Original Message-----
From:=20
linuxppc-embedded-bounces+leoli=3Dfreescale.com@ozlabs.org=20
[mailto:linuxppc-embedded-bounces+leoli=3Dfreescale.com@ozlabs.o
rg] On Behalf Of Jamie Guinan
Sent: Friday, September 01, 2006 12:14 AM
To: linuxppc-embedded@ozlabs.org
Subject: Rattler 8347 and USB 2.0
=20
=20
Greetings,
=20
I have an mpc8347 board here (A&M Rattler 8347).  It shipped with a
2.6.16 patched enough to boot the board, but support for=20
freescale USB 2.0 (ehci) is not present.
=20
Working my way backwards in the mainline kernel tree=20
(2.6.18-rc5), I found drivers/usb/host/ehci-fsl.c, for=20
FreeScale/PPC EHCI support.
=20
In that module, usb_hcd_fsl_probe() requires an initialized=20
"struct fsl_usb2_platform_data", which only appears in=20
arch/powerpc/sysdev/fsl_soc.c, yet the 2.6.16 patch provided=20
puts the board in arch/ppc.
=20
My question is, what would be the best way to go about=20
getting ehci-fsl.c working with this board?
=20
1) Nudge the Rattler port from arch/ppc to arch/powerpc.  One=20
problem with this is that the rattler uses RedBoot, and reading this,
=20
http://ozlabs.org/pipermail/linuxppc-embedded/2006-August/024116.html
=20
it looks like arch/powerpc wants to boot from=20
OpenFirmware-like "flattened device tree" (does RedBoot=20
support this?).

Use a shim which directly builds FDT in kernel to use powerpc arch.

=20
2) Support ehci-fsl.c from arch/ppc.  If arch/ppc is=20
deprecated, that's a bad long-term solution.  And since=20
fsl_soc.c lives under arch/powerpc, that doesn't look good either.

Actually you don't need fsl_soc.c in ppc arch.  There are predefined
platform_device and platform_data in arch/ppc/syslib/mpc83xx_devices.c.
You can add your usb platform_data there easily.