linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Richard Hendricks" <richard.hendricks@motorola.com>
To: Dan Malek <dan@netx4.com>
Cc: Kim Jørgensen <KIJ@infocom.dk>
Subject: Re: Problem with MPC823 LCD driver
Date: Thu, 04 May 2000 13:37:52 -0500	[thread overview]
Message-ID: <3911C380.27BFAB85@motorola.com> (raw)
In-Reply-To: 3911A489.F4A255F6@embeddededge.com


That could be it.  One obvious indicator is that without LCD and
the caches disabled, everything works fine.  If it breaks with the
caches turned on, check your UPM burst tables.  This is where most
mistakes occur.  Also, be sure to bring all the UPM signals back
high at the end of your transactions.

Dan Malek wrote:
>
> Kim Jørgensen wrote:
>
> > I got a custom MPC823E board, and I want to use a LCD display with Linux.
>
> Get the logic analyzer on the bus.......
>
> > Can anyone tell me what is wrong, and how to solve this?
>
> I can make a few guesses.  This has nothing to do with Math Emulation,
> and everything to do with fetching the proper instructions into the
> core.  The LCD controller is a heavy-duty DMA controller that has
> priority over everything to ensure it can keep the display updated
> from system memory.  Since the controller performs large burst mode
> operations, this is a classic example of memory controller or memory
> interface problems.  I suspect the memory timing isn't correct and the
> instructions are just bad memory cycles that can't be properly
> decoded.
>
>         -- Dan
>

--
MPC823 Applications Engineering Development

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

      reply	other threads:[~2000-05-04 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-04 10:38 Problem with MPC823 LCD driver Kim Jørgensen
2000-05-04 16:25 ` Dan Malek
2000-05-04 18:37   ` Richard Hendricks [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=3911C380.27BFAB85@motorola.com \
    --to=richard.hendricks@motorola.com \
    --cc=KIJ@infocom.dk \
    --cc=dan@netx4.com \
    /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).