From: Dan Murphy <dmurphy@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [[PATCH]pandaboard: 1/1] Modification of Elpida DDR2 RAM for Pandaboard-ES Rev B3
Date: Mon, 28 Oct 2013 07:51:50 -0500 [thread overview]
Message-ID: <526E5DE6.1040804@ti.com> (raw)
In-Reply-To: <1382715750-10363-2-git-send-email-hardik.patel@volansystech.com>
On 10/25/2013 10:42 AM, Hardik wrote:
> From: Hardik Patel <hardik.patel@volansystech.com>
>
>
> Signed-off-by: Hardik Patel <hardik.patel@volansystech.com>
> ---
> include/configs/omap4_common.h | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/include/configs/omap4_common.h b/include/configs/omap4_common.h
> index e9f2383..9aa4030 100644
> --- a/include/configs/omap4_common.h
> +++ b/include/configs/omap4_common.h
> @@ -240,7 +240,12 @@
> #define CONFIG_SYS_CACHELINE_SIZE 32
>
> /* Defines for SDRAM init */
> -#define CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS
> +
> +/*
> + * Enable automatic sdram detection
> + * for detecting Elpida RAM on Rev B3
> + */
> +#undef CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS
Nak
This is used on all other Panda revisions.
Why are we just disabling this for all devices when one device is the issue?
And as discussed off line I have an older B3 which boots fine on the uBoot mainline.
So what is the difference between your B3 and my B3? Please answer this to the community or
point to a reference were one can determine what B3 board they have
Dan
>
> #ifndef CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS
> #define CONFIG_SYS_AUTOMATIC_SDRAM_DETECTION
--
------------------
Dan Murphy
next prev parent reply other threads:[~2013-10-28 12:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 15:42 [U-Boot] [[PATCH]pandaboard: 0/1] Modification of Elpida DDR2 RAM for Pandaboard-ES Rev B3 Hardik
2013-10-25 15:42 ` [U-Boot] [[PATCH]pandaboard: 1/1] " Hardik
2013-10-28 12:51 ` Dan Murphy [this message]
2013-10-28 13:04 ` Tom Rini
2013-10-29 14:17 ` Hardik Patel
2013-10-29 15:54 ` Tom Rini
2013-11-14 10:05 ` [U-Boot] [[PATCH v2]pandaboard: 0/1] " Hardik
2013-11-14 10:06 ` Hardik
2013-11-14 10:06 ` [U-Boot] [[PATCH v2]pandaboard: 1/1] " Hardik
2013-11-14 15:29 ` Robert Nelson
2013-11-14 15:41 ` Michael Trimarchi
2013-11-14 16:19 ` Tom Rini
2013-11-14 16:28 ` Michael Trimarchi
2013-11-14 16:32 ` Tom Rini
2013-11-14 18:43 ` Hardik Patel
2013-11-14 18:58 ` Michael Trimarchi
2013-11-14 19:02 ` Tom Rini
2013-11-14 19:41 ` Nishanth Menon
2013-11-14 19:49 ` Tom Rini
2013-11-14 20:26 ` Nishanth Menon
2013-11-21 9:17 ` jmgrimaud
2013-11-27 15:46 ` [U-Boot] [[PATCH v3]pandaboard: 0/1] ARM:OMAP4+: panda-es: Support Rev B3 Elpida DDR2 RAM Hardik
2013-11-27 15:46 ` [U-Boot] [[PATCH v3]pandaboard: 1/1] " Hardik
2013-12-04 22:05 ` [U-Boot] [U-Boot, [PATCH, v3] pandaboard: " Tom Rini
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=526E5DE6.1040804@ti.com \
--to=dmurphy@ti.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