-Original Message-
From: Hilman, Kevin
Sent: Friday, December 02, 2011 11:04 PM
To: Mohammed, Afzal
Cc: Hiremath, Vaibhav; Russell King; linux-omap@vger.kernel.org;
t...@atomide.com; linux-arm-ker...@lists.infradead.org; p...@pwsan.com
Subject: Re: [PATCH-V4 0/3] Introducing TI's
Mohammed, Afzal af...@ti.com writes:
Hi Kevin,
On Thu, Dec 01, 2011 at 20:40:03, Hilman, Kevin wrote:
Hiremath, Vaibhav hvaib...@ti.com writes:
:
We can detect the board using on-board EEPROM, so same mach-id
should work for both EVM and Beagle.
And also going forward with device
-Original Message-
From: Hilman, Kevin
Sent: Thursday, December 01, 2011 5:09 AM
To: Hiremath, Vaibhav; Russell King
Cc: linux-omap@vger.kernel.org; t...@atomide.com; linux-arm-
ker...@lists.infradead.org; p...@pwsan.com
Subject: Re: [PATCH-V4 0/3] Introducing TI's New SoC/board
-V4 0/3] Introducing TI's New SoC/board AM335XEVM
Vaibhav Hiremath hvaib...@ti.com writes:
This patch set adds support for AM335x device having
Cortex-A8 MPU.
Official website - http://www.ti.com/product/am3359
AM335X is treated as another OMAP3 variant, where,
along with existing
Hi Kevin,
On Thu, Dec 01, 2011 at 20:40:03, Hilman, Kevin wrote:
Hiremath, Vaibhav hvaib...@ti.com writes:
:
We can detect the board using on-board EEPROM, so same mach-id
should work for both EVM and Beagle.
And also going forward with device tree approach we may
not need different
