From: Jesper Skov <jskov@redhat.com>
To: Peihong Li <liphhz@yahoo.com>
Cc: ecos-discuss@sources.redhat.com, danc@iobjects.com
Subject: Re: [ECOS] Problem in modify ecos for EDB7312
Date: Tue, 04 Sep 2001 23:44:00 -0000 [thread overview]
Message-ID: <otg0a2kuh5.fsf@zoftcorp.adsl.dk> (raw)
In-Reply-To: <20010905021109.27193.qmail@web20203.mail.yahoo.com>
>>>>> "Peihong" == Peihong Li <liphhz@yahoo.com> writes:
Peihong> Thx, Dan I have setup the registers for SDRAM -
Peihong> SDCONF(@0x80002300)=0x00000522 and
Peihong> SDRFPR(@80002340)=0x00000102. Is there anything else for
Peihong> SDRAM init?
SDRAM init usually involves writing mode data to the SDRAMs themselves
too. Don't ask me how to do it for your board though.
Jesper
next prev parent reply other threads:[~2001-09-04 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00a601c135ae$d0e2f140$4e09a43d@lphnotebook>
2001-09-04 19:11 ` Peihong Li
2001-09-04 23:44 ` Jesper Skov [this message]
2001-09-05 1:54 ` Peihong Li
2001-09-04 11:16 Dan Conti
-- strict thread matches above, loose matches on Subject: below --
2001-09-03 10:56 Peihong Li
2001-09-03 10:45 Peihong Li
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=otg0a2kuh5.fsf@zoftcorp.adsl.dk \
--to=jskov@redhat.com \
--cc=danc@iobjects.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=liphhz@yahoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).