From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <acourbot@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, gnurou@gmail.com
Subject: Re: [PATCH 2/2] ARM: tegra: add device tree for SHIELD
Date: Mon, 12 May 2014 10:41:31 -0600 [thread overview]
Message-ID: <5370F9BB.9040608@wwwdotorg.org> (raw)
In-Reply-To: <1399883209-31169-3-git-send-email-acourbot@nvidia.com>
On 05/12/2014 02:26 AM, Alexandre Courbot wrote:
> NVIDIA SHIELD is a portable Android console embedded a Tegra 4 SoC with
> 2GB RAM and a 720p panel.
>
> The following hardware is enabled by this device tree: UART, eMMC, USB
> (needs external power), PMIC, backlight, joystick, SD card, GPIO keys.
>
> DSI panel, HDMI output, charger, self-powered USB, audio, wifi bluetooth
> are not supported yet but might be by future patches (likely in that
> order).
>
> Touch panel and sensors will probably never be supported.
>
> Initrd addresses are hardcoded to match the static values used by the
> bootloader, since it won't add them for us. All the same, a kernel
> command-line is provided to replace the one passed by the
> bootloader which is filled with garbage.
>
> NVIDIA SHIELD is typically booted with an appended DTB to avoid
> modifications made by the bootloader.
I've applied this one patch to Tegra's for-3.16/dt branch.
prev parent reply other threads:[~2014-05-12 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 8:26 [PATCH 0/2] ARM: tegra: basic support for NVIDIA SHIELD Alexandre Courbot
2014-05-12 8:26 ` [PATCH 1/2] ARM: tegra: joystick input in tegra_defconfig Alexandre Courbot
2014-05-12 16:32 ` Stephen Warren
2014-05-13 3:45 ` Alexandre Courbot
2014-05-13 15:39 ` Stephen Warren
2014-05-12 8:26 ` [PATCH 2/2] ARM: tegra: add device tree for SHIELD Alexandre Courbot
2014-05-12 16:41 ` Stephen Warren [this message]
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=5370F9BB.9040608@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=acourbot@nvidia.com \
--cc=gnurou@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.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