From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] AM35x: Initial support for the processor
Date: Tue, 15 Dec 2009 14:01:34 -0600 [thread overview]
Message-ID: <4B27EB1E.8060704@windriver.com> (raw)
In-Reply-To: <1260902266-26009-1-git-send-email-premi@ti.com>
Sanjeev Premi wrote:
> This patchset adds basic support for the AM35x
> processors. It also ensures that u-boot banner
> shows correct processor at start-up.
>
> Addition of AM35x impacts existing code for OMAP3,
> most patches in this set are applicable to both
> processor families.
>
> The series has been tested on the OMAP3EVM and
> AM3517EVM. To test on AM3517EVM, earlier patches
> posted by Vaibhav are required.
>
> [1] http://lists.denx.de/pipermail/u-boot/2009-November/064670.html
>
>
The am3517 support is not in.
This patchset is dependent on it.
These changes can only be reviewed casually until then.
Vaibhav,
When will next rev of the am3517 changes be posted ?
Tom
next prev parent reply other threads:[~2009-12-15 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 18:37 [U-Boot] [PATCH 0/4] AM35x: Initial support for the processor Sanjeev Premi
2009-12-15 18:37 ` [U-Boot] [PATCH 1/4] AM35x: Introduce support for AM35x processors Sanjeev Premi
2009-12-15 18:37 ` [U-Boot] [PATCH 2/4] OMAP3, AM35x: Detect exact CPU in arch_cpu_init() Sanjeev Premi
2009-12-16 22:11 ` Wolfgang Denk
2009-12-15 18:37 ` [U-Boot] [PATCH 3/4] OMAP3, AM35x: Update function print_cpuinfo() Sanjeev Premi
2009-12-16 22:13 ` Wolfgang Denk
2009-12-15 18:37 ` [U-Boot] [PATCH 4/4] OMAP3, AM35x: Update the checks for CPU revision Sanjeev Premi
2009-12-15 20:01 ` Tom [this message]
2009-12-16 8:45 ` [U-Boot] [PATCH 0/4] AM35x: Initial support for the processor Hiremath, Vaibhav
2010-01-07 14:56 ` Premi, Sanjeev
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=4B27EB1E.8060704@windriver.com \
--to=tom.rix@windriver.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