On 5/14/2014 2:42 PM, Denys Dmytriyenko wrote: > On Tue, May 13, 2014 at 03:32:09PM -0400, [email protected] wrote: >> From: Hao Zhang <[email protected]> >> >> Signed-off-by: Hao Zhang <[email protected]> >> --- >> 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 >> [email protected] >> https://lists.yoctoproject.org/listinfo/meta-ti -- _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
