From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V5 0/4] add TI DA8xx support:
Date: Wed, 11 Nov 2009 20:58:06 -0600 [thread overview]
Message-ID: <4AFB79BE.2090801@windriver.com> (raw)
In-Reply-To: <4AF98238.5030102@gefanuc.com>
Nick Thompson wrote:
> Add initial support for DA8xx SoC's and the spectrum digital DA830 EVM board.
>
> See:
> http://www.ti.com
> http://www.spectrumdigital.com/
>
> DA8xx is similar to DaVinci devices, but has a differing memory map and
> updated peripherals. It is intended that DaVinci drivers will be modified in
> some way to support these differences.
>
> A side effect of this is that there are some legacy code constructs in this
> patch set that are required to utilize the DaVinci drivers as they stand now.
> For example there are some volatiles and memory pointer types defined that are
> no longer considered acceptable.
>
> The new code in this patch set doesn't use these constructs and the remaining
> artefacts can be removed when the DaVinci drivers stop using them.
>
> This patch set is based on code originally from TI.
> ---
> Changes from previous patch set:
>
> #defines of constant variables to lower case
> load registers only as required in clk_get()
>
> This patch set depends on "[PATCH V3] Davinci: add a pin multiplexer
> configuration API" posted on 2009-11-04
Yes it is dependent.
There is a compile error without the pin mux function.
Once the pin multiplex patch is ack-ed then
Ack to this patch set.
Thanks
Tom
>
> Applies to u-boot-ti:
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
next prev parent reply other threads:[~2009-11-12 2:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 15:09 [U-Boot] [PATCH V5 0/4] add TI DA8xx support: Nick Thompson
2009-11-12 2:58 ` Tom [this message]
2009-11-12 11:09 ` Nick Thompson
2009-11-12 13:42 ` Tom
2009-11-12 15:24 ` Paulraj, Sandeep
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=4AFB79BE.2090801@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