linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>
To: "Diego A. Fons" <diegofons@apexar.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Problem with FB
Date: Mon, 28 May 2007 17:18:57 +0200	[thread overview]
Message-ID: <465AF2E1.9090705@rfo.atmel.com> (raw)
In-Reply-To: <4655CC7D.6020600@apexar.com>

Diego A. Fons :
> I was changing the timings values but it seems to get worse, with a set 
> of values the screen moves with every ftp command thet sftp sends!
> Now the values are (it doesn't work either):
> 
> #define AT91_DM9000_NWE_SETUP           (8 << 0)
> #define AT91_DM9000_NCS_WR_SETUP        (4 << 8)
> #define AT91_DM9000_NRD_SETUP           (8 << 16)
> #define AT91_DM9000_NCS_RD_SETUP        (4 << 24)
> 
> #define AT91_DM9000_NWE_PULSE           (16 << 0)
> #define AT91_DM9000_NCS_WR_PULSE        (32 << 8)
> #define AT91_DM9000_NRD_PULSE           (16 << 16)
> #define AT91_DM9000_NCS_RD_PULSE        (32 << 24)
> 
> #define AT91_DM9000_NWE_CYCLE           (36 << 0)
> #define AT91_DM9000_NRD_CYCLE           (36 << 16)
> 
> #define AT91_DM9000_TDF                 (1 << 16)
> 
> I test it with lower and higher values and nothing (with 1 and 127).
> 
> Can you tell me how is it possible that the DM9000 timings interfere 
> with the frame buffer?

Well they both use the SDRam/EBI interface (in fact the ARM926 and the LCD) 
and they may be in conflict some time to get the internal AHB bus (H matrix).
The idea is that one or the other master takes the bus for too long.

What can help us is if you can also check if the fifo underflow UFLWIS 
bit (#4) rises during LDC use.

So, if the LCD is interrupted during a data burst from sdram, it can have 
difficulties to resume its transfer. You can try to lower the configured burst 
length on the LCD : 
ATMEL_LCDC_DMA_BURST_LEN = 4 (so the register field must be written with 0x3) 
instead of 8.

Another option will be to keep the burst length and increase the slot cycle 
in the Matrix interface (from 16->32 or 64). It is the preferred one. This is 
done in the AT91bootstrap but you can do it for testing using a jtag ice.

Keep me informed, Cheers,
-- 
Nicolas Ferre



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  reply	other threads:[~2007-05-28 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 16:45 Problem with FB Diego A. Fons
2007-05-18  7:48 ` Nicolas Ferre
2007-05-18 12:56   ` Diego A. Fons
2007-05-18 13:24     ` Nicolas Ferre
2007-05-24 17:33       ` Diego A. Fons
2007-05-28 15:18         ` Nicolas Ferre [this message]
2007-05-30 13:00           ` Diego A. Fons

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=465AF2E1.9090705@rfo.atmel.com \
    --to=nicolas.ferre@rfo.atmel.com \
    --cc=diegofons@apexar.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).