All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] Add Boundary Devices Nitrogen6X boards
Date: Sun, 10 Mar 2013 08:59:47 +0100	[thread overview]
Message-ID: <20130310075948.035BA200642@gemini.denx.de> (raw)
In-Reply-To: <1362873856-14785-1-git-send-email-eric.nelson@boundarydevices.com>

Dear Eric,

In message <1362873856-14785-1-git-send-email-eric.nelson@boundarydevices.com> you wrote:
>
> +Eric Nelson <eric.nelson@boundarydevices.com>
> +	nitrogen6dl		i.MX6DL		1GB
> +	nitrogen6dl2g		i.MX6DL		2GB
> +	nitrogen6q		i.MX6Q/6D	1GB
> +	nitrogen6q2g    	i.MX6Q/6D	2GB
> +	nitrogen6s		i.MX6S		512MB
> +	nitrogen6s1g		i.MX6S		1GB

Why do we need different configurations for example for nitrogen6dl
and nitrogen6dl2g?  My understanding is that the difference is mainly
the RAM size on the boards?

In this case it should be possible to configure U-Boot for the maximum
possible RAM size (2 GB here?), then have get_ram_size() detect the
actual available amount, and then adjust settings as needed.

At least this is how U-Boot ius supposed to work.

It is a maintenance nightmare if each and every configuration requires
a separate U-Boot image.  We don't want to have this.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A man is not complete until he is married -- then he is finished.

  parent reply	other threads:[~2013-03-10  7:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10  0:04 [U-Boot] [PATCH V2] Add Boundary Devices Nitrogen6X boards Eric Nelson
2013-03-10  0:49 ` Troy Kisky
2013-03-10  8:02   ` Wolfgang Denk
2013-03-10 14:15   ` Eric Nelson
2013-03-10  7:59 ` Wolfgang Denk [this message]
2013-03-10 15:09   ` Eric Nelson
2013-03-10 15:45     ` Wolfgang Denk
2013-03-10 16:25       ` Eric Nelson
2013-03-10 22:03         ` Wolfgang Denk
2013-03-10 23:36           ` Eric Nelson
2013-03-11 11:15             ` Wolfgang Denk
2013-03-11 12:04               ` Stefano Babic
2013-03-11 13:18                 ` Fabio Estevam
2013-03-11 13:44                   ` Stefano Babic
2013-03-11 13:54                     ` Fabio Estevam
2013-03-11 14:02                     ` Eric Nelson
2013-03-11 14:30                       ` Stefano Babic
2013-03-11 14:39                         ` Tom Rini
2013-03-11 13:37               ` Eric Nelson
2013-03-11 16:48                 ` 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=20130310075948.035BA200642@gemini.denx.de \
    --to=wd@denx.de \
    --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.