All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Query related to POST of SDRAM
Date: Tue, 5 Apr 2005 11:05:36 -0400	[thread overview]
Message-ID: <4252A940.1030305@smiths-aerospace.com> (raw)
In-Reply-To: <3D9FDCA910DD4445896A0BE5ECF009D45098F1@bla.satyam.com>

Vikrant_Basotra wrote:
> Hi All,
> 	In file post/memeory.c the following comment is there
> /*
>  * This is 64 bit wide test patterns.  Note that they reside in ROM
>  * (which presumably works) and the tests write them to RAM which may
>  * not work.
>  *
>  * The "otherpattern" is written to drive the data bus to values other
>  * than the test pattern.  This is for detecting floating bus lines.
> *
> */
> This comment gives an hint that this code is specifically for the 64 bit
> wide SDRAM only.
> I ran the same code on the ep8248 board in which the port size of the RAM is
> 32 bits it worked there, didn't throw any error.
> I just want to make it sure that, if the port size of the RAM is 32 bits
> will this test work with out any modifications or  do I have to make some
> changes.
> 
> Regards,
> Vikrant

Confirmed: the processor in hardware does the size translation between 
the register load/store size (64 bits) and the memory bus (could be 
8/16/32/64 bits in various processors and configurations) by doing 
multiple bus cycles as necessary.

The intent of using 64 bit transactions is to stress the bus and use all 
of the bus bits when running a 64 bit wide bus.

gvb

  reply	other threads:[~2005-04-05 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 14:02 [U-Boot-Users] Query related to POST of SDRAM Vikrant_Basotra
2005-04-05 15:05 ` Jerry Van Baren [this message]
2005-04-05 16:19 ` Wolfgang Denk

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=4252A940.1030305@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.