From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>,
Dan Malek <dan@mvista.com>, John Francis <johnfrancsis@yahoo.com>,
Greg Johnsong <johnson@research.canon.com.au>
Subject: structs and defs for IDMA on MPC8xx???
Date: Thu, 27 Sep 2001 16:59:06 +0200 [thread overview]
Message-ID: <3BB33EBA.DF2DCA44@imc-berlin.de> (raw)
Hi there,
are threre any structs for IDMA in the recent kernel sources?
I think of something similar to
I am looking for a "IDMA Buffer Descriptor" similar to
/* Buffer descriptors used by many of the CPM protocols.
*/
typedef struct cpm_buf_desc {
ushort cbd_sc; /* Status and Control */
ushort cbd_datlen; /* Data length in buffer */
uint cbd_bufaddr; /* Buffer address in host memory */
} cbd_t;
I need a way to access the IDMA's parameter RAM, which should be located
at IDMA1 base = IMMR+0x3cc0.
Is there a struct to access the "DMA Channel Mode Register (DCMR)" at
IDMA1 + 0x02?
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 could think of something like
/* Buffer descriptors used by IDMA
*/
typedef struct idma_buf_desc {
ushort ibd_sc; /* Status and Control */
unchar ibd_dfcr; /* destination function code register, s.20.3.4.1*/
unchar ibd_sfcr; /* source function code register */
uint ibd_buflen; /* "number of bytes to transfer" */
uint ibd_srcbuf; /* "points to the beginning of the source buffer" */
uint ibd_destbuf; /* "points to the beginning of the destination
buffer" */
} ibd_t;
TIA.
Cheers,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-09-27 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 14:59 Steven Scholz [this message]
2001-09-27 16:29 ` structs and defs for IDMA on MPC8xx??? Dan Malek
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=3BB33EBA.DF2DCA44@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=dan@mvista.com \
--cc=johnfrancsis@yahoo.com \
--cc=johnson@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 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.