From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Hao Zhang <hzhang@ti.com>, Denys Dmytriyenko <denys@ti.com>
Cc: trini@ti.com, "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH] boot-monitor: add K2L and K2E boot monitor build support
Date: Thu, 15 May 2014 11:38:49 -0400 [thread overview]
Message-ID: <5374DF89.1040105@ti.com> (raw)
In-Reply-To: <5374D81B.7020909@ti.com>
On Thursday 15 May 2014 11:07 AM, Hao Zhang wrote:
> On 5/15/2014 10:54 AM, Denys Dmytriyenko wrote:
>> On Thu, May 15, 2014 at 10:41:52AM -0400, Hao Zhang wrote:
[..]
>>>> Can you clarify if you really want all 3 devices installed all the time or
>>>> do you really want a recipe that installs the boot monitor per device? I
>>>> know you don't currently have 3 machine types so maybe that is what is
>>>> feeding your issue here, but my question is whether you need to have
>>>> separate builds per device.
>>>>
>>>
>>> I want all the 3 boot monitors built and installed all the time in one
>>> recipe, since MCSDK 3.1 supports all the 3 Keystone II devices in the
>>> same release package. This applies to the U-boot (3 U-boot build for all
>>> the 3 Keystone II devices) and Linux kernel DTB.
>>
>> Linux kernel has support for board variations through DTBs, obviously.
>>
>> As of U-boot, in Sitara world we had to manage board variations by detecting
>> the board at runtime. So, the same single binary would work on AM335x-EVM,
>> AM335x-SK, BeagleBone White and BeagleBone Black.
>>
>> I would recommend you working with Tom Rini and doing it similarly, so you
>> don't have to build 3 different binaries for 3 slightly different Keystone
>> baords...
>>
>>
Three boars for same SOC is different than 3 different SOCs with their
own boards. We need to support different u-boot configs for that. And
upstream of the patches work is already in progress with Tom reviewing
the patches.
Regards,
Santosh
next prev parent reply other threads:[~2014-05-15 15:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 18:29 [PATCH] boot-monitor: add K2L and K2E boot monitor build support hzhang
2014-05-14 18:40 ` Denys Dmytriyenko
2014-05-14 18:58 ` Hao Zhang
2014-05-14 19:01 ` Denys Dmytriyenko
2014-05-14 19:55 ` Maupin, Chase
2014-05-14 20:38 ` Hao Zhang
2014-05-15 14:21 ` Maupin, Chase
2014-05-15 14:41 ` Hao Zhang
2014-05-15 14:54 ` Denys Dmytriyenko
2014-05-15 15:07 ` Hao Zhang
2014-05-15 15:38 ` Santosh Shilimkar [this message]
2014-05-15 15:56 ` Maupin, Chase
2014-05-15 16:06 ` Santosh Shilimkar
2014-05-15 16:11 ` Denys Dmytriyenko
2014-05-15 16:14 ` Santosh Shilimkar
2014-05-15 16:22 ` Maupin, Chase
2014-05-15 16:26 ` Hao Zhang
2014-05-15 16:33 ` Denys Dmytriyenko
2014-06-04 13:48 ` Maupin, Chase
2014-06-04 15:04 ` Denys Dmytriyenko
2014-06-05 15:12 ` Denys Dmytriyenko
2014-05-15 15:20 ` Tom Rini
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=5374DF89.1040105@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=denys@ti.com \
--cc=hzhang@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=trini@ti.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.