From: David Gibson <david@gibson.dropbear.id.au>
To: Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [RFC] powerpc: Document new property called interrupt-parents
Date: Thu, 1 Mar 2007 10:38:01 +1100 [thread overview]
Message-ID: <20070228233801.GC3048@localhost.localdomain> (raw)
In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA302AA071F@az33exm25.fsl.freescale.net>
On Wed, Feb 28, 2007 at 08:56:55AM -0700, Yoder Stuart-B08248 wrote:
>
> > -----Original Message-----
> > From: David Gibson [mailto:david@gibson.dropbear.id.au]
> > Sent: Tuesday, February 27, 2007 6:56 PM
> > To: Yoder Stuart-B08248
> > Cc: paulus@samba.org; linuxppc-dev@ozlabs.org
> > Subject: Re: [RFC] powerpc: Document new property called
> > interrupt-parents
> >
> > On Tue, Feb 27, 2007 at 04:54:45PM -0600, Stuart Yoder wrote:
> > >
> > > Document new property called interrupt-parents which can
> > > be used to represent interrupts for devices that route
> > > interrupts to more than one interrupt controller.
> >
> > Well, whatever Segher says, I'm still very concerned about the
> > potential for extra difficulty in debugging with this approach.
>
> The issue, as I understand it, is the potential for an old
> kernel parser to silently misparse a new dev tree with this
> new property.
>
> Do the version and last_comp_version in the blob header
> help here?
Unfortunately not. Those fields version the the serialization format
of the device tree, not the content of the device tree.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-02-28 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 22:54 [RFC] powerpc: Document new property called interrupt-parents Stuart Yoder
2007-02-27 23:40 ` Segher Boessenkool
2007-02-28 0:56 ` David Gibson
2007-02-28 1:09 ` Segher Boessenkool
2007-02-28 15:56 ` Yoder Stuart-B08248
2007-02-28 18:54 ` Segher Boessenkool
2007-02-28 23:38 ` David Gibson [this message]
2007-03-01 1:55 ` Segher Boessenkool
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=20070228233801.GC3048@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=stuart.yoder@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).