> -----Original Message----- > From: Hilman, Kevin > Sent: Friday, December 02, 2011 11:04 PM > To: Mohammed, Afzal > Cc: Hiremath, Vaibhav; Russell King; linux-omap@xxxxxxxxxxxxxxx; > tony@xxxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; paul@xxxxxxxxx > Subject: Re: [PATCH-V4 0/3] Introducing TI's New SoC/board AM335XEVM > > "Mohammed, Afzal" <afzal@xxxxxx> writes: > > > Hi Kevin, > > > > On Thu, Dec 01, 2011 at 20:40:03, Hilman, Kevin wrote: > >> "Hiremath, Vaibhav" <hvaibhav@xxxxxx> 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, Will this solve earlyprintk as well? Thanks, Vaibhav > Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
