linux-kernel - Re: [PATCH 2/2] ARM: tegra: add device tree for SHIELD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 12 May 2014 10:41:31 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Alexandre Courbot <acourbot@...dia.com>,
	Thierry Reding <thierry.reding@...il.com>
CC:	linux-tegra@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, gnurou@...il.com
Subject: Re: [PATCH 2/2] ARM: tegra: add device tree for SHIELD

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/