From mboxrd@z Thu Jan  1 00:00:00 1970
From: Vitaly Andrianov <vitalya@ti.com>
Date: Tue, 29 Mar 2016 07:55:01 -0400
Subject: [U-Boot] [PATCH] configs: ti_armv7_keystone2: make
 SYS_TEXT_BASE configurable at build time
In-Reply-To: <20160328193240.GV23166@bill-the-cat>
References: <1459192559-18880-1-git-send-email-vitalya@ti.com>
 <20160328193240.GV23166@bill-the-cat>
Message-ID: <56FA6D15.5030507@ti.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 03/28/2016 03:32 PM, Tom Rini wrote:
> On Mon, Mar 28, 2016 at 03:15:59PM -0400, Vitaly Andrianov wrote:
>
>> U-boot for general purpose KS2 devices is loaded to the beginning of the
>> internal memory (0x0c000000). Secure devices uses this memory and
>> CONFIG_SYS_TEXT_BASE has to be different for those devices.
>>
>> This commit make this configurable at build time by giving
>> CONFIG_SYS_TEXT_BASE as a command line definition to make command.
>
> I'm interested in getting secure device support going, but it seems like
> we should need more than that, ie something to keep the chain of trust
> going.  I also don't like that we're just overriding this in the command
> line, especially as I expect we'll need other changes too once this gets
> moving forward.  Thanks!
>
Tom,

I reworked boot-monitor for KS2 secure devices and CONFIG_SYS_TEXT_BASE 
is only change required to support KS2 secure devices.

Thanks,
Vitaly