linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>,
	Dan Malek <dan@embeddededge.com>,
	Frank Przybylski <frank.przybylski@vas-gmbh.de>
Subject: Re: MPC8xx and IDMA !?!?
Date: Fri, 19 Apr 2002 14:00:49 +0200	[thread overview]
Message-ID: <3CC006F1.5940B04E@imc-berlin.de> (raw)
In-Reply-To: 3CBD321A.60CE328@imc-berlin.de


To whom it may concern,

> a while ago (aprox. kernel 2.4.11) I succesfully played around with IDMA
> on MPC855/860.
> ...
> The code is NOT working on recent kernels (I pulled it yesterday).
> I set up the IDMA. Trigger DREQ0 using a GPIO pin. SDMACK1 is going LOW
> but then instead of toggeling it just stays LOW. And instead of
> transfering data the MPC8xx just hangs.
>
> Have there been changes in the DPRAM layout ..?

I (think I) figured out the problem:

I use
	m8xx_cpm_dpalloc( sizeof(idma_bd_t) );

to allocate space for the buffer descriptors in the DP ram.

The User Man says "Note that IBASE should be burst-aligned (divisible by
16)"
(Does the English "should be" means "have to be, otherwise everything
goes wrong!"???)

The older kernel versions always returned (by pure accident?) a
burst-aligned address (%16) (e.g. 0x850 offset from dpmem start). So
everything was fine.

The newer kernels return (by pure accident?) a NON burst-aligned address
(e.g. 0x0918) und the IDMA crashes.

So my workaround for now is to allocate more than I need and correct the
value for IBASE like
	ibase += ibase % 16

Could anyone think of a better solution? Since I waste at least 16 bytes
in the DPRAM.

BTW:
Where is Wolfgangs m8xx_cpm_dpfree() !?!?
I can't find it in the recent source trees.

Cheers,

Steven

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

  reply	other threads:[~2002-04-19 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17  8:28 MPC8xx and IDMA !?!? Steven Scholz
2002-04-19 12:00 ` Steven Scholz [this message]
2002-04-19 18:15   ` Dan Malek
2002-04-23 15:39     ` Steven Scholz

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=3CC006F1.5940B04E@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=dan@embeddededge.com \
    --cc=frank.przybylski@vas-gmbh.de \
    --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).