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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 03 Jan 2013 14:16:41 -0700
From:	Stephen Warren <>
To:	Thierry Reding <>
CC:	Hiroshi Doyu <>, Andrew Lunn <>,
	Russell King <>,
	Jason Cooper <>,
	John Stultz <>,,,,
	Rob Herring <>,
	Grant Likely <>,
	Olof Johansson <>, Rob Landley <>,, Thomas Gleixner <>,
	Shawn Guo <>,
	Jean-Christophe PLAGNIOL-VILLARD <>,
Subject: Re: [PATCH 0/9] ARM: Initial support for Tegra 114 SoC.

On 01/03/2013 02:00 PM, Thierry Reding wrote:
> On Thu, Dec 20, 2012 at 11:43:58AM +0200, Hiroshi Doyu wrote:
>> Hi,
>> This patchset adds initial support for the NVIDIA's new Tegra
>> 114 SoC (T114) based on the ARM Cortex-A15 MP. It has the minimal
>> support to allow the kernel to boot up into shell console. This
>> can be used as a basis for adding other device drivers for this
>> SoC. Currently there are 2 evaluation boards available, "Dalmore"
>> and "Pluto".
>> This patchset is against Stephen Warren's linux-next_common
>> branch:
>> git://
>> linux-next_common
>> For those who want to try:
>> $ make ARCH=arm tegra_defconfig $ scripts/config -e
>> -d CPU_IDLE
> I wonder, what's the reason for disabling DRM? And while on the
> topic, are there any plans to release a Tegra114 TRM?

AFAIK, the HW is basically compatible with previous chips, so I expect
to see a DRM driver for it show up once all the various more basic
devices are supported.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists