linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Guinan <guinan@bluebutton.com>
To: linuxppc-embedded@ozlabs.org
Subject: Rattler 8347 and USB 2.0
Date: Thu, 31 Aug 2006 12:14:12 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0608291535260.23035@gemini.home.net> (raw)


Greetings,

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 freescale USB 
2.0 (ehci) is not present.

Working my way backwards in the mainline kernel tree (2.6.18-rc5), I 
found drivers/usb/host/ehci-fsl.c, for FreeScale/PPC EHCI support.

In that module, usb_hcd_fsl_probe() requires an initialized "struct 
fsl_usb2_platform_data", which only appears in 
arch/powerpc/sysdev/fsl_soc.c, yet the 2.6.16 patch provided puts the 
board in arch/ppc.

My question is, what would be the best way to go about getting 
ehci-fsl.c working with this board?

1) Nudge the Rattler port from arch/ppc to arch/powerpc.  One problem
with this is that the rattler uses RedBoot, and reading this,

http://ozlabs.org/pipermail/linuxppc-embedded/2006-August/024116.html

it looks like arch/powerpc wants to boot from OpenFirmware-like 
"flattened device tree" (does RedBoot support this?).

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

Thoughts?

-Jamie

             reply	other threads:[~2006-08-31 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-31 16:14 Jamie Guinan [this message]
2006-09-01  2:54 ` Rattler 8347 and USB 2.0 Li Yang-r58472
2006-12-01  6:54   ` Jamie Guinan
  -- strict thread matches above, loose matches on Subject: below --
2006-12-01 12:33 Claus Gindhart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0608291535260.23035@gemini.home.net \
    --to=guinan@bluebutton.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).