All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Kelly <mike@cogcomp.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: USB Host controller for MPC8548e board
Date: Tue, 13 Feb 2007 20:39:15 -0500	[thread overview]
Message-ID: <6.2.5.6.2.20070213202913.03e23eb0@cogcomp.com> (raw)
In-Reply-To: <C7F96CD5-4CB7-48E3-ABF5-17E1685AAC24@kernel.crashing.org>

The reason I asked here is that they are in the kernel and seem to be 
as well supported.  I was
just more concerned if there were any PowerPC specific issues.  We 
are likely going ahead
with the NEC (since that is what was used on the G5 MAC's, I think), 
and we'll find out just how
well they work!  That's what prototypes are for.

Thanks,
Michael

At 08:19 PM 2/13/2007, Kumar Gala wrote:

>On Feb 13, 2007, at 6:21 PM, Michael Kelly wrote:
>
>>Hello all.  We are in the process of designing an MPC8548e board.  We
>>wish to add
>>USB host via either the NXP ISP1561 or NEC upd720101.  They are
>>both OHCI and
>>EHCI.
>
>Haven't worked with either of this, you're probably better asking
>about this on the linux-usb list.
>
>>Is there any general advice on one over the other or even if it is
>>realistic to have a USB
>>host controller on a big endian processor?
>
>There shouldn't be any issue with having a USB controller on a big- 
>endian processor.
>
>If your connecting them over PCI it should pretty easy to get them up
>and running.
>
>- k
>
>

Michael J. Kelly
VP Engineering
Cogent Computer Systems, Inc.
17 Industrial Dr.
Smithfield, RI 02917 USA
tel: 401-223-3441, fax: 401-223-3442
email: mike@cogcomp.com
alternate email: mkelly6505@hotmail.com
web: www.cogcomp.com

  reply	other threads:[~2007-02-14  1:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  0:21 USB Host controller for MPC8548e board Michael Kelly
2007-02-14  1:19 ` Kumar Gala
2007-02-14  1:39   ` Michael Kelly [this message]
2007-02-14  1:48 ` Benjamin Herrenschmidt
2007-02-14  2:09   ` Michael Kelly

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=6.2.5.6.2.20070213202913.03e23eb0@cogcomp.com \
    --to=mike@cogcomp.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.