linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Greg Johnson <gjohnson@research.canon.com.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC860 Embedded Planet IDMA Support
Date: Wed, 23 Feb 2000 21:40:11 -0500	[thread overview]
Message-ID: <38B49A0B.92CEC283@netx4.com> (raw)
In-Reply-To: 20000224002220.90CE07C8@elph.research.canon.com.au


Greg Johnson wrote:


> Kernel 2.2.13 that we are using on the MPC860 does not have support
> for IDMA which we need.

I haven't and don't know of anyone that has.  Providing the
software is the easy part, just use existing CPM DPRAM allocation
functions for the BDs and either overload or create new BD
structures in commproc.h.

The harder part is the hardware interface.  The /DREQx and /RTSx
multiplex on the same pin, which prohibits cool protocols like
Ethernet on the SCC ports when using IDMA.

The IDMA isn't terribly efficient, so it either runs in "background"
mode or at a high priority.  If you are using the CPM for other
tasks, the IDMA may not move much data for you in background
mode, or will starve other communication tasks when run at
a higher priority.  Make sure you calculate CPM loading and
everything fits.

In the complete system architecture, it is more efficient to
program the UPM to control the device and use burst mode programmed
I/O cycles from the PPC core.  The IDMA cycles are long, even
with devices that can respond quickly, and you tie up the
System bus, U bus, internal RISC bus, effectively eliminating
any overlapped processing by any functional unit within the part.
At least with programmed I/O, the CPM can still do its
communication thing.

Also, since no one uses IDMA (there may be a lesson here :-) the
CPM microcode patches remap parameter spaces into the IDMA
locations.  Sometimes this is selectable, and you may have to
chase down places where this is done and customize to suit
your application.

It may work for you.  Just make sure you consider all of the
alternatives.


	-- Dan

P.S.  Have you signed up with Embedded Planet and received their
expansion guidelines?  Lots of technical tidbits there that can
make your life more enjoyable.

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

      reply	other threads:[~2000-02-24  2:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-24  0:22 MPC860 Embedded Planet IDMA Support Greg Johnson
2000-02-24  2:40 ` Dan Malek [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=38B49A0B.92CEC283@netx4.com \
    --to=dan@netx4.com \
    --cc=gjohnson@research.canon.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).