From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/7] Tegra114: Add arch-tegra114 include files
Date: Fri, 18 Jan 2013 16:54:58 -0700 [thread overview]
Message-ID: <50F9E0D2.3000403@wwwdotorg.org> (raw)
In-Reply-To: <1358543537-18035-2-git-send-email-twarren@nvidia.com>
On 01/18/2013 02:12 PM, Tom Warren wrote:
> Common Tegra files are in arch-tegra, shared between T20/T30/T114.
> Tegra114-specific headers are in arch-tegra114. Note that some of
> these will be filled in as more T114 support is added (drivers,
> WB/LP0 support, etc.).
> diff --git a/arch/arm/include/asm/arch-tegra/tegra.h b/arch/arm/include/asm/arch-tegra/tegra.h
> index 013a3c5..2dbe6a3 100644
> --- a/arch/arm/include/asm/arch-tegra/tegra.h
> +++ b/arch/arm/include/asm/arch-tegra/tegra.h
> @@ -73,6 +73,7 @@ enum {
> SKU_ID_AP25E = 0x1b,
> SKU_ID_T25E = 0x1c,
> SKU_ID_T30 = 0x81, /* Cardhu value */
> + SKU_ID_T114 = 0x00, /* Dalmore value */
I believe a SKU ID of 0 indicates an unfused or engineering part. I'll
try to find the relevant email and forward it to you off-list. As such,
I think it'll save us trouble in the future if you simply rename that
SKU_ID_T114_UNFUSED/GENERIC/ENG/ENGINEERING to make it explicit what
this means. You should probably talk to someone internally to confirm
the best terminology to use here; probably whoever originally sent the
email that I'll try to forward to you. I think you can make such a
trivial symbol renaming change when you apply the patch, without
reposting the patches, unless any other changes are needed.
next prev parent reply other threads:[~2013-01-18 23:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 21:12 [U-Boot] [PATCH v2 0/7] Add support for NVIDIA Tegra114 SoC Tom Warren
2013-01-18 21:12 ` [U-Boot] [PATCH v2 1/7] Tegra114: Add arch-tegra114 include files Tom Warren
2013-01-18 23:54 ` Stephen Warren [this message]
2013-01-22 20:44 ` Tom Warren
2013-01-22 21:02 ` Stephen Warren
2013-01-18 21:12 ` [U-Boot] [PATCH v2 2/7] Tegra114: Add AVP (arm720t) files Tom Warren
2013-01-19 0:01 ` Stephen Warren
2013-01-19 0:09 ` Stephen Warren
2013-01-22 20:46 ` Tom Warren
2013-01-22 21:02 ` Stephen Warren
2013-01-18 21:12 ` [U-Boot] [PATCH v2 3/7] Tegra114: Add CPU (armv7) files Tom Warren
2013-01-22 20:06 ` Simon Glass
2013-01-18 21:12 ` [U-Boot] [PATCH v2 4/7] Tegra114: Add common CPU (shared) files Tom Warren
2013-01-22 20:54 ` Simon Glass
2013-01-22 21:37 ` Tom Warren
2013-01-22 21:45 ` Simon Glass
2013-01-22 21:49 ` Tom Warren
2013-01-22 21:53 ` Simon Glass
2013-01-18 21:12 ` [U-Boot] [PATCH v2 5/7] Tegra114: Dalmore: Add DT files Tom Warren
2013-01-18 21:12 ` [U-Boot] [PATCH v2 6/7] Tegra114: Add generic Tegra114 build support Tom Warren
2013-01-18 21:12 ` [U-Boot] [PATCH v2 7/7] Tegra114: Add/enable Dalmore build (T114 reference board) Tom Warren
2013-01-19 0:03 ` 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=50F9E0D2.3000403@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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.