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 Note: Paul advised to post to linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, but it never made to LAKML, even though I sent couple of times and got a reply "Is being held until the list moderator can review it for approval. The reason it is being held: Message has a suspicious header" Regards Afzal -- 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
