All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Vaibhav Hiremath <hvaibhav@ti.com>, Russell King <rmk@arm.linux.org.uk>
Cc: tony@atomide.com, paul@pwsan.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH-V4 0/3] Introducing TI's New SoC/board AM335XEVM
Date: Wed, 30 Nov 2011 15:39:16 -0800	[thread overview]
Message-ID: <878vmxxjrv.fsf@ti.com> (raw)
In-Reply-To: <1320946837-32507-1-git-send-email-hvaibhav@ti.com> (Vaibhav Hiremath's message of "Thu, 10 Nov 2011 23:10:34 +0530")

Vaibhav Hiremath <hvaibhav@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 cpu class OMAP34XX, new cpu class AM33XX is created
> and the respective type is AM335X, which is newly added device in
> the family.
> This means, cpu_is_omap34xx(), cpu_is_am33xx() and
> cpu_is_am335x() checks return success for AM335X.
>
> Also, I have validated OMAP3 boot test with this patch-series on OMAP3EVM.

After fixing the minor comment on patch 3/3, feel free to add:

Reviewed-by: Kevin Hilman <khilman@ti.com>

Also, I was surprised to discover that this booted on my (recently
arrived) BeagleBone.  It seems that u-boot (from Angstrom) is passing
the machine ID of the AM335x EVM[1], even though there is another
machine ID for the BeagleBone[2].  Is that expected?

I also see that the mach-types for this are in Russell's for-next
branch.  In order for us to merge this into Tony's master branch, we'll
need to see if Russell can pull the mach-types updates into
devel-stable.  Russell?

Kevin

[1] http://www.arm.linux.org.uk/developer/machines/list.php?id=3589
[2] http://www.arm.linux.org.uk/developer/machines/list.php?id=3808

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: Wed, 30 Nov 2011 15:39:16 -0800	[thread overview]
Message-ID: <878vmxxjrv.fsf@ti.com> (raw)
In-Reply-To: <1320946837-32507-1-git-send-email-hvaibhav@ti.com> (Vaibhav Hiremath's message of "Thu, 10 Nov 2011 23:10:34 +0530")

Vaibhav Hiremath <hvaibhav@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 cpu class OMAP34XX, new cpu class AM33XX is created
> and the respective type is AM335X, which is newly added device in
> the family.
> This means, cpu_is_omap34xx(), cpu_is_am33xx() and
> cpu_is_am335x() checks return success for AM335X.
>
> Also, I have validated OMAP3 boot test with this patch-series on OMAP3EVM.

After fixing the minor comment on patch 3/3, feel free to add:

Reviewed-by: Kevin Hilman <khilman@ti.com>

Also, I was surprised to discover that this booted on my (recently
arrived) BeagleBone.  It seems that u-boot (from Angstrom) is passing
the machine ID of the AM335x EVM[1], even though there is another
machine ID for the BeagleBone[2].  Is that expected?

I also see that the mach-types for this are in Russell's for-next
branch.  In order for us to merge this into Tony's master branch, we'll
need to see if Russell can pull the mach-types updates into
devel-stable.  Russell?

Kevin

[1] http://www.arm.linux.org.uk/developer/machines/list.php?id=3589
[2] http://www.arm.linux.org.uk/developer/machines/list.php?id=3808

  parent reply	other threads:[~2011-11-30 23:39 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 ` Kevin Hilman [this message]
2011-11-30 23:39   ` [PATCH-V4 0/3] Introducing TI's New SoC/board AM335XEVM 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
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=878vmxxjrv.fsf@ti.com \
    --to=khilman@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.