All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com
Subject: Re: [PATCH OSSTEST 2/2] uboot: make flask loading address host property
Date: Wed, 25 Mar 2015 10:18:30 +0000	[thread overview]
Message-ID: <1427278710.10784.46.camel@citrix.com> (raw)
In-Reply-To: <1427197552-29042-3-git-send-email-wei.liu2@citrix.com>

On Tue, 2015-03-24 at 11:45 +0000, Wei Liu wrote:
> Please set host property 'UBootSetFlaskAddrR' to 0x1200000.

Sigh, I wasn't having a very good day yesterday, since I completely
failed to do this.

I've now done:
OSSTEST_CONFIG=production-config ./mg-hosts setprops  marilith-n4 marilith-n5 -- UBootSetFlaskAddrR 0x1200000

and will make a note to figure out and set good addresses for the ARM
boards in the new colo.

Since flight 36721 hasn't run any x86 build jobs yet and it has already
failed the test-armhf-armhf*-xsm jobs I've killed it so it gets another
bite of the cherry.

Ian.

> ---
>  Osstest/Debian.pm | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm
> index b829878..9f7705e 100644
> --- a/Osstest/Debian.pm
> +++ b/Osstest/Debian.pm
> @@ -158,10 +158,16 @@ sub setupboot_uboot ($$$$) {
>  	    # Use the flaskpolicy from tools build job because we might
>  	    # want to test cross releases policy compatibility.
>  	    my $flaskpolicy = get_runvar('flaskpolicy',$r{buildjob});
> +	    my $flask_policy_addr_r =
> +		get_host_property($ho, 'UBootSetFlaskAddrR', undef);
> +	    my $set_flask_addr_r =
> +		$flask_policy_addr_r ?
> +		"setenv flask_policy_addr_r $flask_policy_addr_r" : "";
> +
>  	    $xenhopt .= " flask=enforcing";
>  	    $flask_commands = <<END;
>  
> -setenv flask_policy_addr_r 0x1200000
> +${set_flask_addr_r}
>  flaskpolicy=`readlink -f /boot/$flaskpolicy`
>  ext2load scsi 0 \\\${flask_policy_addr_r} \$flaskpolicy
>  fdt mknod /chosen module\@2

  parent reply	other threads:[~2015-03-25 10:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 11:45 [PATCH OSSTEST 0/2] Uboot patches for XSM test case Wei Liu
2015-03-24 11:45 ` [PATCH OSSTEST 1/2] uboot: use "readlink -f" Wei Liu
2015-03-24 12:23   ` Ian Campbell
2015-03-27  9:28   ` Ian Campbell
2015-03-27 10:46     ` [PATCH OSSTEST v2 1/2] uboot: do not use readlink on xsm policy Ian Campbell
2015-03-31 12:27       ` Ian Jackson
2015-03-27 10:46     ` [PATCH OSSTEST v2 2/2] uboot: make flask loading address host property Ian Campbell
2015-03-27 16:31     ` [PATCH OSSTEST 1/2] uboot: use "readlink -f" Atom2
2015-03-27 17:06       ` Ian Campbell
2015-03-24 11:45 ` [PATCH OSSTEST 2/2] uboot: make flask loading address host property Wei Liu
2015-03-24 12:23   ` Ian Campbell
2015-03-25 10:18   ` Ian Campbell [this message]
2015-03-27 14:54   ` Ian Campbell

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=1427278710.10784.46.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.