From: Hao Zhang <hzhang@ti.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] keystone: u-boot: change UBOOT_MACHINE name to "k2hk_evm_config"
Date: Wed, 14 May 2014 15:02:45 -0400 [thread overview]
Message-ID: <5373BDD5.3060809@ti.com> (raw)
In-Reply-To: <20140514184257.GP18053@edge>
On 5/14/2014 2:42 PM, Denys Dmytriyenko wrote:
> On Tue, May 13, 2014 at 03:32:09PM -0400, hzhang@ti.com wrote:
>> From: Hao Zhang <hzhang@ti.com>
>>
>> Signed-off-by: Hao Zhang <hzhang@ti.com>
>> ---
>> conf/machine/include/keystone.inc | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/conf/machine/include/keystone.inc b/conf/machine/include/keystone.inc
>> index b961ad3..63f069c 100644
>> --- a/conf/machine/include/keystone.inc
>> +++ b/conf/machine/include/keystone.inc
>> @@ -12,7 +12,7 @@ MACHINE_KERNEL_PR = "r7"
>>
>> KERNEL_IMAGETYPE = "uImage"
>>
>> -UBOOT_MACHINE = "tci6638_evm_config"
>> +UBOOT_MACHINE = "k2hk_evm_config"
>
> What's the difference? Which one do you use for MCSDK builds? Are all the
> versions and variants covered by that config?
>
>
k2hk is a generic device name for both CI and mass market product
(tcixxxx is a CI part number), and should be used.
I will submit a 2nd patch to add k2l_evm_config and k2e_evm_config for
k2l and k2e devices. Is there any example code to support U-boot build
on multiple devices with the same Keystone machine?
>> UBOOT_ENTRYPOINT = "0x80008000"
>> UBOOT_LOADADDRESS = "0x80008000"
>> --
>> 1.7.9.5
>>
>> --
>> _______________________________________________
>> meta-ti mailing list
>> meta-ti@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti
prev parent reply other threads:[~2014-05-14 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 19:32 [PATCH] keystone: u-boot: change UBOOT_MACHINE name to "k2hk_evm_config" hzhang
2014-05-14 18:42 ` Denys Dmytriyenko
2014-05-14 19:02 ` Hao Zhang [this message]
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=5373BDD5.3060809@ti.com \
--to=hzhang@ti.com \
--cc=denys@ti.com \
--cc=meta-ti@yoctoproject.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 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.