From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ARM: tegra: support SKU b1 of Tegra30
Date: Fri, 20 Sep 2013 10:03:33 -0600 [thread overview]
Message-ID: <523C71D5.1060509@wwwdotorg.org> (raw)
In-Reply-To: <20130920124501.GA23804@ulmo>
On 09/20/2013 06:45 AM, Thierry Reding wrote:
> On Wed, Sep 04, 2013 at 11:59:44AM -0600, Stephen Warren wrote:
>> On 09/04/2013 07:00 AM, Alban Bedel wrote:
>>> Add the Tegra30 SKU b1 and treat it like other Tegra30 chips.
>>
>> CC'ing the Tegra maintainer would be helpful (Tom Warren; I CC'd
>> him here)
>>
>>> diff --git a/arch/arm/cpu/tegra-common/ap.c
>>> b/arch/arm/cpu/tegra-common/ap.c
>>
>>> @@ -71,6 +71,7 @@ int tegra_get_chip_sku(void) switch (sku_id)
>>> { case SKU_ID_T33: case SKU_ID_T30: + case SKU_ID_T30MQS:
>>
>> Where does the name "T30MQS" come from? Tom, can you verify what
>> we call the SKUs internally?
>
> It seems like this is indeed called T30MQS internally. Actually
> it's called TM30MQS-A3. I can provide an internal reference if
> required.
As long as it's been checked, I don't think we need to document it. In
which case, IIRC, the patch was fine.
next prev parent reply other threads:[~2013-09-20 16:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 13:00 [U-Boot] [PATCH 1/2] ARM: tegra: support SKU b1 of Tegra30 Alban Bedel
2013-09-04 13:00 ` [U-Boot] [PATCH 2/2] ARM: tegra: Add the Tamonten™ NG Evaluation Carrier board Alban Bedel
2013-09-04 18:05 ` Stephen Warren
2013-09-05 12:46 ` Alban Bedel
2013-09-05 19:15 ` Stephen Warren
2013-09-04 17:59 ` [U-Boot] [PATCH 1/2] ARM: tegra: support SKU b1 of Tegra30 Stephen Warren
2013-09-20 12:45 ` Thierry Reding
2013-09-20 16:03 ` Stephen Warren [this message]
2013-09-20 17:57 ` Tom Warren
2013-09-23 8:51 ` Alban Bedel
2013-09-24 0:23 ` Tom Warren
2013-10-17 9:29 ` Alban Bedel
2013-10-17 10:50 ` Thierry Reding
2013-10-17 14:59 ` Stephen Warren
2013-10-17 15:26 ` Thierry Reding
2013-10-17 15:45 ` Tom 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=523C71D5.1060509@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox