From: Dan Murphy <dmurphy@ti.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] k2hk-hs-evm: add new machine config
Date: Thu, 30 Mar 2017 06:44:54 -0500 [thread overview]
Message-ID: <58DCEFB6.3000001@ti.com> (raw)
In-Reply-To: <20170329141445.GB11364@edge>
Denys
On 03/29/2017 09:14 AM, Denys Dmytriyenko wrote:
> On Wed, Mar 29, 2017 at 07:03:35AM -0500, Dan Murphy wrote:
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>> ---
>> conf/machine/k2hk-hs-evm.conf | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>> create mode 100644 conf/machine/k2hk-hs-evm.conf
>>
>> diff --git a/conf/machine/k2hk-hs-evm.conf b/conf/machine/k2hk-hs-evm.conf
>> new file mode 100644
>> index 0000000..e0b11eb
>> --- /dev/null
>> +++ b/conf/machine/k2hk-hs-evm.conf
>> @@ -0,0 +1,14 @@
>> +#@TYPE: Machine
>> +#@NAME: Keystone 2 K2HK HS EVM
>> +#@DESCRIPTION: Machine configuration for the TI Keystone 2 K2HK HS EVM
>> +
>> +require conf/machine/k2hk-evm.conf
>> +
>> +UBOOT_MACHINE = "k2e_hs_evm_config"
> Dan,
>
> Is k2e used here on purpose because k2hk defconfig is not ready yet?
I was using that for testing I must have deleted the wrong line when I was cleaning up.
I will fix it
Dan
>
>> +UBOOT_ENTRYPOINT = "0x82000000"
>> +UBOOT_LOADADDRESS = "0x82000000"
>> +UBOOT_RD_LOADADDRESS = "0x84000000"
>> +UBOOT_RD_ENTRYPOINT = "0x84000000"
>> +
>> +TI_SECURE_DEV_PKG = "${TI_SECURE_DEV_PKG_CAT}/k2hk"
>> --
>> 2.7.3
>>
>> --
>> _______________________________________________
>> meta-ti mailing list
>> meta-ti@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti
--
------------------
Dan Murphy
prev parent reply other threads:[~2017-03-30 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 12:03 [PATCH] k2hk-hs-evm: add new machine config Dan Murphy
2017-03-29 14:14 ` Denys Dmytriyenko
2017-03-30 11:44 ` Dan Murphy [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=58DCEFB6.3000001@ti.com \
--to=dmurphy@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.