From: zhanglei459 <zhanglei459@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Can CPU write video memory directly?
Date: Tue, 20 May 2008 06:54:14 -0700 (PDT) [thread overview]
Message-ID: <17340898.post@talk.nabble.com> (raw)
Hi all,
Now I am debugging video chip MB86297A.Reference to hardware manual,I
have configured PCI registers ,Carmine Control registers and DRAM Control
registers under U-boot , other modules registers have not been configured.I
dont know how to verify DRAM is configured correctly. When I "md" video
memory,they are all zero,and after I "mm" video memory,they are "md" still
display all zero .Are DRAM Control registers configured wrong? Does CPU
modify video memory?
Thanks!
--
View this message in context: http://www.nabble.com/Can-CPU-write-video-memory-directly--tp17340898p17340898.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next reply other threads:[~2008-05-20 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 13:54 zhanglei459 [this message]
2008-05-23 14:49 ` [U-Boot-Users] Can CPU write video memory directly? Detlev Zundel
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=17340898.post@talk.nabble.com \
--to=zhanglei459@gmail.com \
--cc=u-boot@lists.denx.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