From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH-V4 0/3] Introducing TI's New SoC/board AM335XEVM Date: Fri, 02 Dec 2011 09:33:34 -0800 Message-ID: <87aa7akhe9.fsf@ti.com> References: <1320946837-32507-1-git-send-email-hvaibhav@ti.com> <878vmxxjrv.fsf@ti.com> <79CD15C6BA57404B839C016229A409A80474FD@DBDE01.ent.ti.com> <878vmws4z8.fsf@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from na3sys009aog120.obsmtp.com ([74.125.149.140]:40938 "EHLO na3sys009aog120.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757170Ab1LBRdi (ORCPT ); Fri, 2 Dec 2011 12:33:38 -0500 Received: by mail-gx0-f169.google.com with SMTP id q4so3368234ggn.28 for ; Fri, 02 Dec 2011 09:33:37 -0800 (PST) In-Reply-To: (Afzal Mohammed's message of "Fri, 2 Dec 2011 04:36:02 +0000") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Mohammed, Afzal" Cc: "Hiremath, Vaibhav" , Russell King , "linux-omap@vger.kernel.org" , "tony@atomide.com" , "linux-arm-kernel@lists.infradead.org" , "paul@pwsan.com" "Mohammed, Afzal" writes: > Hi Kevin, > > On Thu, Dec 01, 2011 at 20:40:03, Hilman, Kevin wrote: >> "Hiremath, Vaibhav" 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 id's, right? >> >> Right, which is why I'm wondering why are there sevral new AM33x >> mach-types when only one of them is being used: >> >> 3684 TI AM335X IA EVM am335xiaevm Afzal Mohammed >> 3589 TI AM335X EVM am335xevm Vaibhav Bedia >> 3808 Beaglebone Board beaglebone Steven Kipisz >> >> Russell has been trying to cleanup athe mach-types, so if these others >> are not going to be used, I suggest they be deleted. > > "3684-TI AM335X IA EVM" is required as IA EVM uses a different UART, > because of which early prints can't be captured, problem mentioned > in http://marc.info/?l=linux-omap&m=131286938723617&w=2 This problem will be solved by using the device tree. Kevin