Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Chase Maupin <Chase.Maupin@ti.com>
Subject: Re: [PATCH 5/5] am45x-evm: Add am45x-evm machine configuration
Date: Tue, 05 Apr 2011 12:37:47 -0400	[thread overview]
Message-ID: <20110405163747.GA7168@denix.org> (raw)
In-Reply-To: <1302018111-20799-5-git-send-email-Chase.Maupin@ti.com>

On Tue, Apr 05, 2011 at 10:41:51AM -0500, Chase Maupin wrote:
> * Added a new machine configuration for the am45x-evm device.
> * This machine currently mimics the omap4430-panda configuration
>   during the prototyping phase but is expected to change as the
>   hardware and software evolves.
> * The am45x-evm machine type is used to allow differentiating
>   software components to be build and packaged (i.e. task lists)
>   as well as to account for differences with the omap4430-panda
>   device in the future.

Chase,

This would have been better explained in a cover letter for all the 5 patches, 
as I was reading through the first 4 and wondering why do you use panda 
remnants, until I got to the 5th one... :)

FYI, there are new repos on arago ready to be populated for linux-am45x and 
u-boot-am45x, so need to switch corresponding recipes in the future...

> Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>

Acked-by: Denys Dmytriyenko <denys@ti.com>

> ---
>  conf/machine/am45x-evm.conf |   10 ++++++++++
>  1 files changed, 10 insertions(+), 0 deletions(-)
>  create mode 100644 conf/machine/am45x-evm.conf
> 
> diff --git a/conf/machine/am45x-evm.conf b/conf/machine/am45x-evm.conf
> new file mode 100644
> index 0000000..3597d37
> --- /dev/null
> +++ b/conf/machine/am45x-evm.conf
> @@ -0,0 +1,10 @@
> +#@TYPE: Machine
> +#@NAME: AM45X EVM
> +#@DESCRIPTION: Machine configuration for the AM45x EVM
> +
> +# Currently the am45x-evm machine type mimics the panda
> +# machine for its configuration.  This is expected to change
> +# as the hardware and software evolves.  Currently the unique
> +# machine type is used to differentiate software stack being
> +# built for the two devices.
> +require conf/machine/omap4430-panda.conf
> -- 
> 1.7.0.4
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2011-04-05 16:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 15:41 [PATCH 1/5] linux-omap4: Add support for am45x-evm machine Chase Maupin
2011-04-05 15:41 ` [PATCH 2/5] u-boot: " Chase Maupin
2011-04-05 16:38   ` Denys Dmytriyenko
2011-04-05 15:41 ` [PATCH 3/5] sort: Add support for am45x-evm machine type Chase Maupin
2011-04-05 16:39   ` Denys Dmytriyenko
2011-04-05 15:41 ` [PATCH 4/5] alsa-state: " Chase Maupin
2011-04-05 16:39   ` Denys Dmytriyenko
2011-04-05 15:41 ` [PATCH 5/5] am45x-evm: Add am45x-evm machine configuration Chase Maupin
2011-04-05 16:37   ` Denys Dmytriyenko [this message]
2011-04-05 18:11     ` Maupin, Chase
2011-04-05 16:38 ` [PATCH 1/5] linux-omap4: Add support for am45x-evm machine Denys Dmytriyenko

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=20110405163747.GA7168@denix.org \
    --to=denis@denix.org \
    --cc=Chase.Maupin@ti.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox