From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc64-dev@ozlabs.org, Tzachi Perelstein <tzachi@marvell.com>,
u-boot-users@lists.sourceforge.net,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Booting the Linux/ppc64 kernel without Open Firmware HOWTO (v3)
Date: Tue, 24 May 2005 09:50:30 +0200 [thread overview]
Message-ID: <78325f65fc807da213be423c20ce6dcd@kernel.crashing.org> (raw)
In-Reply-To: <1116909351.4992.19.camel@gaston>
> +/*
> + * The Open Firmware 1275 specification states properties must be 31
> bytes or
> + * less, however not all firmwares obey this. Make it 64 bytes to be
> safe.
> + */
Not true. There is no restriction on the length of properties
(or property _names_, which I guess is what you meant). There
is the 31-char restriction on _node_ names, though (and the node
name is only the part before the optional @ or : -- and at a
minimum, the part after @ but before : is needed to disambiguate
the node).
I didn't review the rest of the code, sorry.
Segher
next prev parent reply other threads:[~2005-05-24 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 4:34 Booting the Linux/ppc64 kernel without Open Firmware HOWTO (v3) Benjamin Herrenschmidt
2005-05-24 4:35 ` Benjamin Herrenschmidt
2005-05-24 7:50 ` Segher Boessenkool [this message]
2005-05-24 7:55 ` Benjamin Herrenschmidt
2005-05-24 8:01 ` Segher Boessenkool
2005-05-24 15:11 ` Jon Loeliger
2005-05-24 21:48 ` Benjamin Herrenschmidt
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=78325f65fc807da213be423c20ce6dcd@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=tzachi@marvell.com \
--cc=u-boot-users@lists.sourceforge.net \
/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).