From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 02/13] tegra20: move tegra20 SoC code to arch/arm/cpu/tegra20-common
Date: Fri, 22 Jun 2012 11:43:59 -0700 [thread overview]
Message-ID: <20120622184359.GB17621@nvidia.com> (raw)
In-Reply-To: <4FE4B65B.3050702@wwwdotorg.org>
On Fri, Jun 22, 2012 at 11:15:55AM -0700, Stephen Warren wrote:
> On 06/21/2012 06:00 PM, Allen Martin wrote:
> > In preparation for splitting out the armv4t code from tegra20, move
> > the tegra20 SoC code to arch/arm/cpu/tegra20-common. This code will
> > be compiled armv4t for the arm7tdmi and armv7 for the cortex A9.
> >
> > Signed-off-by: Allen Martin <amartin@nvidia.com>
>
> The only thing I wonder here is whether tegra20-common or tegra-common
> is a better location, given that we'll eventually add Tegra30 support,
> and some of the code might be shared.
>
> Still, we can address that issue when we add Tegra30 support I think, so.
>
> Acked-by: Stephen Warren <swarren@wwwdotorg.org>
I think Simon had the same feedback in a earlier version. My response
was that pulling out the tegra20/tegra30 commonalities will require
much more refactoring and is better left to a separate patch series.
-Allen
--
nvpublic
next prev parent reply other threads:[~2012-06-22 18:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 0:00 [U-Boot] [PATCH v4 0/13] split tegra20 arm7 code into separate SPL Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 01/13] tegra20: rename tegra2 -> tegra20 Allen Martin
2012-06-22 18:13 ` Stephen Warren
2012-06-22 18:41 ` Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 02/13] tegra20: move tegra20 SoC code to arch/arm/cpu/tegra20-common Allen Martin
2012-06-22 18:15 ` Stephen Warren
2012-06-22 18:43 ` Allen Martin [this message]
2012-06-22 0:00 ` [U-Boot] [PATCH v4 03/13] tegra20: rename CONFIG_MACH_TEGRA_GENERIC Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 04/13] tegra20: tec: add tegra20-common-post.h Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 05/13] tegra20: plutux: change obj directory mkdir commands Allen Martin
2012-06-25 17:39 ` Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 06/13] mkconfig: add support for SPL CPU Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 07/13] ARM: Fix arm720t SPL build Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 08/13] tegra20: remove timer_init from " Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 09/13] ARM: add tegra20 support to arm720t Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 10/13] tegra20: add u-boot-t2.bin target Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 11/13] tegra20: move SDRAM param save to later in boot Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 12/13] tegra20: enable SPL for tegra20 boards Allen Martin
2012-06-22 0:00 ` [U-Boot] [PATCH v4 13/13] tegra20: Remove armv4t build flags Allen Martin
2012-06-22 18:27 ` Stephen Warren
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=20120622184359.GB17621@nvidia.com \
--to=amartin@nvidia.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