From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Yoder Stuart-B08248" <stuart.yoder@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [RFC] powerpc: Document new property called interrupt-parents
Date: Wed, 28 Feb 2007 19:54:31 +0100 [thread overview]
Message-ID: <6687f608d80f1f82105c38bbb56c6628@kernel.crashing.org> (raw)
In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA302AA071F@az33exm25.fsl.freescale.net>
>> 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.
Exactly. Note that such such an old parser will misparse
the "interrupt-array" property as well, namely, not at all.
Debugging *could* be a bit easier though, who knows.
> Do the version and last_comp_version in the blob header
> help here?
That's not what those version fields are for.
The real solution is to just not use too old kernels with
too new a firmware/bootloader/device tree. This issue
has existed for since forever and is in no way specific
to adding new OF bindings, or specific to Linux, or
anything like that.
> It's more of a general problem.
Quite so.
It might be worthwhile to add a device tree property
"minimum-linux-version" (in the tree root) that the kernel
will parse and complain about loudly if it doesn't match;
at a minimum it will make it super-duper clear to users
of a DTS with that property which combos work. Documentation
rules ;-)
Segher
next prev parent reply other threads:[~2007-02-28 18:54 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 [this message]
2007-02-28 23:38 ` David Gibson
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=6687f608d80f1f82105c38bbb56c6628@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=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).