public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Doug Maxey <dwm@maxeymade•com>
To: Paul Nasrat <pnasrat@redhat•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] powerpc: Add FSL SEC node to documentation
Date: Sat, 25 Mar 2006 16:27:19 -0600	[thread overview]
Message-ID: <200603252227.k2PMRJ57026730@falcon30.maxeymade.com> (raw)
In-Reply-To: <1142976221.2751.22.camel@enki.eridu>


On Tue, 21 Mar 2006 16:23:41 EST, Paul Nasrat wrote:
>On Tue, 2006-03-21 at 13:28 -0600, Hollis Blanchard wrote:
>> On Tue, 2006-03-21 at 12:25 -0600, Kumar Gala wrote:
>> > On Mar 20, 2006, at 8:14 PM, Hollis Blanchard wrote:
>
>> > > Have you consulted with any other vendors regarding these  
>> > > properties? I know
>> > > there is no IEEE1275 binding for these sorts of devices, but we can  
>> > > at least
>> > > attempt to standardize it (even in the absence of the Open Firmware  
>> > > Working
>> > > Group)...
>> > 
>> > Beyond the device_type, I'm not sure if there is much more one could  
>> > standardize one.  The other fields that Kim spec'd are either generic  
>> > OF fields (reg, interrupts, etc.) or specific to the Freescale devices.
>> 
>> The device_type and compatible properties are exactly what I'm talking
>> about.
>
>The Working Group lists still exist but are pretty dead.  I agree we
>really want to ensure that both OF based and dtc based new hardware is
>consistent.  I'm not sure how we want to do this, but we can document in
>Documentation and then use eg SLOF to mock out the OF interfaces and
>create proposals and kick some life into the OF working group.  

Sorry for the delayed reply, my procmail filter was pumping mails to
the old list name without telling me. :)

Other than IBM, Motorola, and possibly Sun, what groups are using 
OFW on new platforms anymore?  

Power.org may be a vehicle to publish.  

The Power TSC leader indicated a willingness to look into a process to 
get out some purely internal bindings (at the moment) that _really_ 
need some fresh air to flourish.

++doug

  reply	other threads:[~2006-03-25 23:15 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
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 [this message]
  -- 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=200603252227.k2PMRJ57026730@falcon30.maxeymade.com \
    --to=dwm@maxeymade$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=pnasrat@redhat$(echo .)com \
    /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