LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: "FIXED-TERM Seeh Thomas (BEG/EMS1)"
	<fixed-term.Thomas.Seeh@de.bosch.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: MPC5200B and USB
Date: Wed, 14 Oct 2009 12:21:27 -0600	[thread overview]
Message-ID: <fa686aa40910141121r74ea411dwd602685a98eb31a5@mail.gmail.com> (raw)
In-Reply-To: <6E9D235B18CE694399D781F05D9C42E7A035ADDD@SI-MBX11.de.bosch.com>

On Wed, Oct 14, 2009 at 6:57 AM, FIXED-TERM Seeh Thomas (BEG/EMS1)
<fixed-term.Thomas.Seeh@de.bosch.com> wrote:
> Hello everyone,
>
> I'm working on a project to get USB ready on a MPC5200B based board.
> On this board I'm not using Linux (but MQX), but my question is not related
> to Linux.
> It's more specific to USB and OHCI.
> I will communicate with a Mass Storage Device and therefor the control
> transfer works fine.
> The Mass Storage Device has two endpoints for bulk transfer, one IN (from
> device to host) and
> one OUT (from host to device).
>
> If I want to communicate with the device should I have two endpoints on the
> host side too?

Sounds like you need to brush up on how USB works.  The host
controller can talk to any endpoint on any device, and it schedules
the transfers for them.  There are no host-side endpoints like there
are on the device.

This question is very off-topic for this list.  You should refer to
the USB standards documentation or look for a USB specific mailing
list.  Please don't ask non-Linux questions on a Linux mailing list.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

      reply	other threads:[~2009-10-14 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14 12:57 MPC5200B and USB FIXED-TERM Seeh Thomas (BEG/EMS1)
2009-10-14 18:21 ` Grant Likely [this message]

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=fa686aa40910141121r74ea411dwd602685a98eb31a5@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=fixed-term.Thomas.Seeh@de.bosch.com \
    --cc=linuxppc-dev@lists.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