From: Kevin Hilman <khilman@ti.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: "Hiremath, Vaibhav" <hvaibhav@ti.com>,
Russell King <rmk@arm.linux.org.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"paul@pwsan.com" <paul@pwsan.com>
Subject: Re: [PATCH-V4 0/3] Introducing TI's New SoC/board AM335XEVM
Date: Fri, 02 Dec 2011 09:33:34 -0800 [thread overview]
Message-ID: <87aa7akhe9.fsf@ti.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A902847B@DBDE01.ent.ti.com> (Afzal Mohammed's message of "Fri, 2 Dec 2011 04:36:02 +0000")
"Mohammed, Afzal" <afzal@ti.com> writes:
> Hi Kevin,
>
> On Thu, Dec 01, 2011 at 20:40:03, Hilman, Kevin wrote:
>> "Hiremath, Vaibhav" <hvaibhav@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 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
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-V4 0/3] Introducing TI's New SoC/board AM335XEVM
Date: Fri, 02 Dec 2011 09:33:34 -0800 [thread overview]
Message-ID: <87aa7akhe9.fsf@ti.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A902847B@DBDE01.ent.ti.com> (Afzal Mohammed's message of "Fri, 2 Dec 2011 04:36:02 +0000")
"Mohammed, Afzal" <afzal@ti.com> writes:
> Hi Kevin,
>
> On Thu, Dec 01, 2011 at 20:40:03, Hilman, Kevin wrote:
>> "Hiremath, Vaibhav" <hvaibhav@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 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
next prev parent reply other threads:[~2011-12-02 17:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 17:40 [PATCH-V4 0/3] Introducing TI's New SoC/board AM335XEVM Vaibhav Hiremath
2011-11-10 17:40 ` Vaibhav Hiremath
2011-11-10 17:40 ` [PATCH-V4 1/3] arm:omap:am33xx: Update common OMAP machine specific sources Vaibhav Hiremath
2011-11-10 17:40 ` Vaibhav Hiremath
2011-11-10 17:40 ` [PATCH-V4 2/3] arm:omap:am33xx: Add AM335XEVM machine support Vaibhav Hiremath
2011-11-10 17:40 ` Vaibhav Hiremath
2011-11-10 17:40 ` [PATCH-V4 3/3] arm:omap:am33xx: Add low level debugging support Vaibhav Hiremath
2011-11-10 17:40 ` Vaibhav Hiremath
2011-11-30 23:33 ` Kevin Hilman
2011-11-30 23:33 ` Kevin Hilman
2011-12-01 10:52 ` Hiremath, Vaibhav
2011-12-01 10:52 ` Hiremath, Vaibhav
2011-12-01 15:00 ` Kevin Hilman
2011-12-01 15:00 ` Kevin Hilman
2011-11-30 23:39 ` [PATCH-V4 0/3] Introducing TI's New SoC/board AM335XEVM Kevin Hilman
2011-11-30 23:39 ` Kevin Hilman
2011-12-01 11:07 ` Hiremath, Vaibhav
2011-12-01 11:07 ` Hiremath, Vaibhav
2011-12-01 15:10 ` Kevin Hilman
2011-12-01 15:10 ` Kevin Hilman
2011-12-02 4:36 ` Mohammed, Afzal
2011-12-02 4:36 ` Mohammed, Afzal
2011-12-02 17:33 ` Kevin Hilman [this message]
2011-12-02 17:33 ` Kevin Hilman
2011-12-20 12:15 ` Hiremath, Vaibhav
2011-12-20 12:15 ` Hiremath, Vaibhav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aa7akhe9.fsf@ti.com \
--to=khilman@ti.com \
--cc=afzal@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rmk@arm.linux.org.uk \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.