From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2]: OMAP3 SPL updates
Date: Sun, 09 Oct 2011 11:21:44 +0200 [thread overview]
Message-ID: <4E9167A8.7070806@compulab.co.il> (raw)
In-Reply-To: <CA+M6bXmOX-fHWRGxD+RFqrS0SPkRQJWgSPdsUXJqnTksNNw-ig@mail.gmail.com>
On 10/07/11 02:28, Tom Rini wrote:
> On Tue, Oct 4, 2011 at 7:59 AM, Tom Rini <trini@ti.com> wrote:
>> Hey all,
>>
>> The following short series does two things. First, it re-works where
>> we do memory initalization in SPL for OMAP3 to be board-specific.
>> This is needed since in many cases (beagleboard, omap3evm) what timings
>> we set depend on what hardware we detect ourself to be running on. Second,
>> along those same lines what omap_rev_string tells us is doing to be
>> board specific as well so provide a weak version in the common omap SPL
>> code and lets it be replaced as needed.
>
> Please disregard this version, I need to do a full v3 with the right
> set of board_early_sdrc_init, sorry for the noise.
While I was looking at the series, I've got similar thoughts.
May be this should be facilitated by providing kind of framework
for the board file only to set the right settings and not duplicate
the board_early_sdrc_init() function (with changed values)?
--
Regards,
Igor.
next prev parent reply other threads:[~2011-10-09 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 14:59 [U-Boot] [PATCH 0/2]: OMAP3 SPL updates Tom Rini
2011-10-04 14:59 ` [U-Boot] [PATCH 1/2] OMAP3 SPL: Rework memory initalization and devkit 8000 support Tom Rini
2011-10-06 21:08 ` Wolfgang Denk
2011-10-07 0:12 ` [U-Boot] [PATCH v2 1/1] " Tom Rini
2011-10-04 14:59 ` [U-Boot] [PATCH 2/2] OMAP3 SPL: Provide weak omap_rev_string Tom Rini
2011-10-07 0:28 ` [U-Boot] [PATCH 0/2]: OMAP3 SPL updates Tom Rini
2011-10-09 9:21 ` Igor Grinberg [this message]
2011-10-10 3:01 ` Tom Rini
2011-10-10 7:22 ` Igor Grinberg
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=4E9167A8.7070806@compulab.co.il \
--to=grinberg@compulab.co.il \
--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