linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>,
	John Francis <johnfrancsis@yahoo.com>,
	Greg Johnsong <johnson@research.canon.com.au>
Subject: Re: structs and defs for IDMA on MPC8xx???
Date: Thu, 27 Sep 2001 12:29:04 -0400	[thread overview]
Message-ID: <3BB353D0.F4AA371D@mvista.com> (raw)
In-Reply-To: 3BB33EBA.DF2DCA44@imc-berlin.de


Steven Scholz wrote:

> are threre any structs for IDMA in the recent kernel sources?

No, they would be in 'commproc.h'.  Again, just use a similar
method to all of the other device drivers for the CPM.  There
is a standard BD structure that is part of all devices for
DMA purposes, and simply add the information needed by IDMA.

> I need a way to access the IDMA's parameter RAM,

Don't confuse "parameter ram" and IDMA buffer descriptors.  If
you notice, the parameter ram is defined as the offset into the
appropriate pages of the CPM memory.  This information for IDMA
is not currently defined in 'commproc.h' and you will need to do that.

> I know Greg Johnson <gjohnson@research.canon.com.au> proposed some stuff
> last year. But they never made it into the linuxppc_2_4_devel, did they?

I don't recall anyone sending a patch to do this.  If they did,
I apologize for missing it and I'll look through the archives to
find it.

> I could think of something like
>
> /* Buffer descriptors used by IDMA
> */
> typedef struct idma_buf_desc {

There you go, the IDMA buffer descriptor.  Why didn't you just
edit commproc.h to include this, get it working, and send a patch :-)?

Thanks.


	-- Dan

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

  reply	other threads:[~2001-09-27 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 14:59 structs and defs for IDMA on MPC8xx??? Steven Scholz
2001-09-27 16:29 ` Dan Malek [this message]
2001-09-27 17:07   ` Steven Scholz
2001-09-27 17:34     ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2001-10-02  2:42 Subodh Nijsure

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=3BB353D0.F4AA371D@mvista.com \
    --to=dan@mvista.com \
    --cc=johnfrancsis@yahoo.com \
    --cc=johnson@research.canon.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=steven.scholz@imc-berlin.de \
    /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).