public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vitaly Andrianov <vitalya@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] configs: ti_armv7_keystone2: make SYS_TEXT_BASE configurable at build time
Date: Tue, 29 Mar 2016 07:55:01 -0400	[thread overview]
Message-ID: <56FA6D15.5030507@ti.com> (raw)
In-Reply-To: <20160328193240.GV23166@bill-the-cat>

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

  reply	other threads:[~2016-03-29 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 19:15 [U-Boot] [PATCH] configs: ti_armv7_keystone2: make SYS_TEXT_BASE configurable at build time Vitaly Andrianov
2016-03-28 19:32 ` Tom Rini
2016-03-29 11:55   ` Vitaly Andrianov [this message]
2016-04-02  1:59 ` [U-Boot] " 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=56FA6D15.5030507@ti.com \
    --to=vitalya@ti.com \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox