From: Hollis Blanchard <hollis@penguinppc•org>
To: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] powerpc: Add FSL SEC node to documentation
Date: Mon, 20 Mar 2006 20:14:43 -0600 [thread overview]
Message-ID: <200603202014.44879.hollis@penguinppc.org> (raw)
In-Reply-To: <20060320195945.004fdf26.kim.phillips@freescale.com>
On Monday 20 March 2006 19:59, Kim Phillips wrote:
> diff --git a/Documentation/powerpc/booting-without-of.txt=20
b/Documentation/powerpc/booting-without-of.txt
> index d02c649..72f3241 100644
> --- a/Documentation/powerpc/booting-without-of.txt
> +++ b/Documentation/powerpc/booting-without-of.txt
> @@ -1365,6 +1365,79 @@ platforms are moved over to use the flat
> =A0=A0=A0=A0=A0=A0};
> =A0
> =A0
> + =A0 g) Freescale SOC SEC Security Engines
> +
> + =A0 Required properties:
> +
> + =A0 =A0- device_type : Should be "crypto"
> + =A0 =A0- model : Model of the device. =A0Should be "SEC1" or "SEC2"
> + =A0 =A0- compatible : Should be "talitos"
[snip]
Have you consulted with any other vendors regarding these properties? I kno=
w=20
there is no IEEE1275 binding for these sorts of devices, but we can at leas=
t=20
attempt to standardize it (even in the absence of the Open Firmware Working=
=20
Group)...
=2DHollis
next prev parent reply other threads:[~2006-03-21 2:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 1:59 [PATCH] powerpc: Add FSL SEC node to documentation Kim Phillips
2006-03-21 2:14 ` Hollis Blanchard [this message]
2006-03-21 17:48 ` Kim Phillips
2006-03-21 18:21 ` Kumar Gala
2006-03-22 1:10 ` Kim Phillips
2006-03-22 4:09 ` Paul Mackerras
2006-03-21 18:25 ` Kumar Gala
2006-03-21 19:28 ` Hollis Blanchard
2006-03-21 21:23 ` Paul Nasrat
2006-03-25 22:27 ` Doug Maxey
-- strict thread matches above, loose matches on Subject: below --
2006-03-22 20:39 Kim Phillips
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=200603202014.44879.hollis@penguinppc.org \
--to=hollis@penguinppc$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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