From: Alexandre Courbot <acourbot@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gnurou@gmail.com" <gnurou@gmail.com>
Subject: Re: [PATCH] ARM: tegra: add device tree for SHIELD
Date: Mon, 3 Mar 2014 12:53:13 +0900 [thread overview]
Message-ID: <5313FCA9.9020809@nvidia.com> (raw)
In-Reply-To: <1393818596-26775-1-git-send-email-acourbot@nvidia.com>
On 03/03/2014 12:49 PM, Alexandre Courbot wrote:
> Add a device tree for NVIDIA SHIELD. The set of enabled features is
> still minimal with no display option and USB requiring external power.
>
> A default kernel command-line as well as initrd addresses are hardcoded
> to match the static values the bootloader is known to use. This allows
> booting from an appended DTB without having to alter it at boot time,
> since the bootloader has no Device Tree support.
>
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> ---
Forgot to specify this is a v2, apologies for the inconvenience.
Changes since v1:
- Comment on the memory range
- Removed nodes for currently unsupported hardware (i.e. wifi)
next prev parent reply other threads:[~2014-03-03 3:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 3:49 Alexandre Courbot
2014-03-03 3:53 ` Alexandre Courbot [this message]
2014-03-03 17:00 ` Stephen Warren
2014-03-04 1:24 ` Alexandre Courbot
-- strict thread matches above, loose matches on Subject: below --
2014-02-24 10:26 Alexandre Courbot
2014-02-24 18:53 ` Stephen Warren
2014-02-25 2:13 ` Alexandre Courbot
2014-02-25 9:52 ` Arend van Spriel
2014-02-26 4:52 ` Alexandre Courbot
2014-02-26 21:10 ` Arend van Spriel
2014-02-25 22:38 ` Stephen Warren
2014-02-26 4:58 ` Alexandre Courbot
2014-02-26 5:02 ` Stephen Warren
2014-02-26 5:12 ` Alexandre Courbot
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=5313FCA9.9020809@nvidia.com \
--to=acourbot@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
/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
Powered by JetHome