From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/6] [v2] powerpc/85xx: Add P5040 processor support
Date: Wed, 3 Oct 2012 14:48:42 -0500 [thread overview]
Message-ID: <506C969A.3050005@freescale.com> (raw)
In-Reply-To: <20121001131213.816cf5a652ed1f258ba8c7da@freescale.com>
Kim Phillips wrote:
>> > Support for hardware virtualization and partitioning enforcement
>> > Extra privileged level for hypervisor support
>> > QorIQ Trust Architecture 1.1
>> > Secure boot, secure debug, tamper detection, volatile key storage
> same comment as I made before - make this marketing text relevant to
> u-boot, e.g., list what devices this patch supports.
I guess we'll have to agree to disagree. I always put information like
this when adding new soc/board support.
>> + SET_SEC_DECO_LIODN_ENTRY(0, 97, 98),
>> + SET_SEC_DECO_LIODN_ENTRY(1, 99, 100),
>> +};
> NACK - the SEC in the p5040 has four DECOs, not two.
I should have the proper LIODN information later today.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-10-03 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 14:06 [U-Boot] [PATCH 1/6] powerpc/mpc85xx: fix Unicode characters in release.S Timur Tabi
2012-10-01 14:06 ` [U-Boot] [PATCH 2/6] powerpc/85xx: introduce SET_PCI_LIODN_BASE, for setting PCI LIODNs Timur Tabi
2012-10-01 14:06 ` [U-Boot] [PATCH 3/6] powerpc/85xx: move SRIO configuration out of corenet_ds.h Timur Tabi
2012-10-01 14:06 ` [U-Boot] [PATCH 4/6] [v2] powerpc/85xx: Add P5040 processor support Timur Tabi
2012-10-01 18:12 ` Kim Phillips
2012-10-03 19:48 ` Timur Tabi [this message]
2012-10-01 14:06 ` [U-Boot] [PATCH 5/6] powerpc/p5040ds: add per pci endpoint liodn offset list Timur Tabi
2012-10-01 14:06 ` [U-Boot] [PATCH 6/6] [v2] powerpc/85xx: add support for the Freescale P5040DS Superhydra reference board Timur Tabi
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=506C969A.3050005@freescale.com \
--to=timur@freescale.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 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.