From: Dan Malek <dan@mvista.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: structs and defs for IDMA on MPC8xx???
Date: Thu, 27 Sep 2001 13:34:56 -0400 [thread overview]
Message-ID: <3BB36340.F207E365@mvista.com> (raw)
In-Reply-To: 3BB35CD3.6D152CA6@imc-berlin.de
Steven Scholz wrote:
> Have you ever use IDMA?
Yes.
> .... I think there is a significanct difference
> between SDMA and IDMA.
Well, yes. IDMA (like all CPM devices) use the SDMA function
to access memory.....
> The "standard BD structure" doesn't help much for IDMA, does it?
> So it's not that easy. I already had a look at enet.c...
The IDMA uses the same logical sequence of events and processing
as all CPM devices. No, the bits aren't exactly the same in the
structure, but if that is all you are concerned about you are
missing the forest and worried about the trees. The same logical
steps for initializing the parameter ram, allocating DP memory,
initializing BDs, wiring interrupts, and managing BDs is the same
for all CPM devices. I apologize for not having the trivial data
structures ready for you to use.......
> It was in April last year!
Sorry I missed it.
> I'll attach what I have so far. It's basicly the patch sent by Greg. I
> am about to check all these defines again.
Well, if this is it, I now understand why it was never integrated.
I don't simply update GPL header files without the corresponding
code that needs those changes. Wait until you actually have working
driver and I'll update everything at once.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-27 17:34 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
2001-09-27 17:07 ` Steven Scholz
2001-09-27 17:34 ` Dan Malek [this message]
-- 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=3BB36340.F207E365@mvista.com \
--to=dan@mvista.com \
--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).