linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Steve Calfee <calfee@kerbango.com>
To: Brad Parker <brad@parker.boston.ma.us>,
	Brad Hards <bradh@dynamite.com.au>
Cc: Björn Lundberg <bjorn.lundberg@inu.se>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: commproc.c
Date: Mon, 06 Mar 2000 11:45:19 -0800	[thread overview]
Message-ID: <4.2.2.20000306113008.00a67be0@mail.kerbango.com> (raw)
In-Reply-To: <200003061622.LAA34076@p2.parker.boston.ma.us>


At 11:22 AM 3/6/00 -0500, Brad Parker wrote:


>Brad Hards wrote:
>...
> >The 850 Users Manual contains info (including how to program) on the USB
> >host as part of CPM doco - it is chapter 32, and has been recently
> >updated:
> >http://www.mot.com/SPS/RISC/netcomm/aesop/mpc8XX/850/32_USB.pdf
> >
> >The whole users manual is linked off:
> >http://www.mot.com/SPS/RISC/netcomm/docs/pubs/850UM.html
>
>I beg to differ - the docs don't really cover host mode at all and
>don't explain a number of things you might need to know to make it
>work.  I've sent feedback to MOT about this already.  The docs are
>really minimal and not very helpful for host mode.  They are just
>barely enough for function mode.
>
>-brad
I eagerly read these docs, but they just repeat the info in the PPC 823
manual.

The whole USB host architecture is bizarre, it looks like it was crafted by
someone who understood uarts and serial I/O very well, but USB only
marginally. For example, the idea of having separate areas for receive and
transmit BDs, for a host controlled half-duplex communication line adds
complexity and makes no sense. At least you can get around it in software.
Also, the idea that a NAK or STAL is an error that should stop transmission
of a BD list is a major roadblock to getting any bandwidth out of the USB
Bus. Right now I am trying to figure out why I don't get a TX interrupt
after sending a IN PID with the I bit set in the BD.....

Software timers for SOF can get to USB spec +- .5 microseconds 99.9% of the
time (NFS shuts off interrupts for long periods of time occasionally). The
SOF timing will probably be good enough for most devices. Philips audio
Isochronous devices require +- 1 USB bit times (=1/12,000,000=.083
microseconds), too tight for Linux timer interrupts.

Enough complaining, I am convinced that a reasonably functional USB host
stack is possible.

Steve

Steve Calfee	--	embedded systems consultant
calfee@home.com
Kerbango phone: (408) 517-3355
home office ph: (510) 657-6039


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-03-06 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-02 20:20 commproc.c Steve Calfee
2000-03-02 16:22 ` commproc.c Dan Malek
2000-03-03 23:22   ` commproc.c Steve Calfee
2000-03-04 20:10 ` commproc.c Björn Lundberg
2000-03-05 15:58   ` commproc.c Brad Hards
2000-03-06 10:37     ` commproc.c Björn Lundberg
2000-03-06 16:22     ` commproc.c Brad Parker
2000-03-06 19:45       ` Steve Calfee [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=4.2.2.20000306113008.00a67be0@mail.kerbango.com \
    --to=calfee@kerbango.com \
    --cc=bjorn.lundberg@inu.se \
    --cc=brad@parker.boston.ma.us \
    --cc=bradh@dynamite.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.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).