From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@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 17:55:02 +1000 [thread overview]
Message-ID: <1116921302.6395.6.camel@gaston> (raw)
In-Reply-To: <78325f65fc807da213be423c20ce6dcd@kernel.crashing.org>
On Tue, 2005-05-24 at 09:50 +0200, Segher Boessenkool wrote:
> > +/*
> > + * 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).
Yes, we meant names, and yes, there is a limit of 31 characters + 0,
that is 32 bytes (see "3.2.2.1.1 Property names" in 1275. BTW. Do you
have a useable version of this document ? mine is a totally broken PDF
made from a crappy .ps :)
IBM firmware broke that limit in a couple of places though...
> 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).
Yes, I know all that.
> I didn't review the rest of the code, sorry.
No worries :)
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Booting the Linux/ppc64 kernel without Open Firmware HOWTO (v3)
Date: Tue, 24 May 2005 17:55:02 +1000 [thread overview]
Message-ID: <1116921302.6395.6.camel@gaston> (raw)
In-Reply-To: <78325f65fc807da213be423c20ce6dcd@kernel.crashing.org>
On Tue, 2005-05-24 at 09:50 +0200, Segher Boessenkool wrote:
> > +/*
> > + * 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).
Yes, we meant names, and yes, there is a limit of 31 characters + 0,
that is 32 bytes (see "3.2.2.1.1 Property names" in 1275. BTW. Do you
have a useable version of this document ? mine is a totally broken PDF
made from a crappy .ps :)
IBM firmware broke that limit in a couple of places though...
> 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).
Yes, I know all that.
> I didn't review the rest of the code, sorry.
No worries :)
Ben.
next prev parent reply other threads:[~2005-05-24 7:55 UTC|newest]
Thread overview: 14+ 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:34 ` [U-Boot-Users] " Benjamin Herrenschmidt
2005-05-24 4:35 ` Benjamin Herrenschmidt
2005-05-24 4:35 ` [U-Boot-Users] " Benjamin Herrenschmidt
2005-05-24 7:50 ` Segher Boessenkool
2005-05-24 7:50 ` [U-Boot-Users] " Segher Boessenkool
2005-05-24 7:55 ` Benjamin Herrenschmidt [this message]
2005-05-24 7:55 ` Benjamin Herrenschmidt
2005-05-24 8:01 ` Segher Boessenkool
2005-05-24 8:01 ` [U-Boot-Users] " Segher Boessenkool
2005-05-24 15:11 ` Jon Loeliger
2005-05-24 15:11 ` [U-Boot-Users] " Jon Loeliger
2005-05-24 21:48 ` Benjamin Herrenschmidt
2005-05-24 21:48 ` [U-Boot-Users] " 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=1116921302.6395.6.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=segher@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.