From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Tzachi Perelstein <tzachi@marvell.com>,
u-boot-users@lists.sourceforge.net, linuxppc64-dev@ozlabs.org
Subject: Re: Booting the Linux/ppc64 kernel without Open Firmware HOWTO (v3)
Date: Tue, 24 May 2005 10:01:32 +0200 [thread overview]
Message-ID: <c7e35bb102646dae463a41a5110d5dfa@kernel.crashing.org> (raw)
In-Reply-To: <1116921302.6395.6.camel@gaston>
> Yes, we meant names, and yes, there is a limit of 31 characters + 0,
Nah, it's thirty-one chars, not 31. Sorry for missing this.
> 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 :)
Mine is a perfectly working PDF from a perfectly working PS. I'll send
it to you.
> IBM firmware broke that limit in a couple of places though...
That's what happens if there isn't a testsuite anywhere.
> Yes, I know all that.
Good :-)
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@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 10:01:32 +0200 [thread overview]
Message-ID: <c7e35bb102646dae463a41a5110d5dfa@kernel.crashing.org> (raw)
In-Reply-To: <1116921302.6395.6.camel@gaston>
> Yes, we meant names, and yes, there is a limit of 31 characters + 0,
Nah, it's thirty-one chars, not 31. Sorry for missing this.
> 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 :)
Mine is a perfectly working PDF from a perfectly working PS. I'll send
it to you.
> IBM firmware broke that limit in a couple of places though...
That's what happens if there isn't a testsuite anywhere.
> Yes, I know all that.
Good :-)
Segher
next prev parent reply other threads:[~2005-05-24 8:01 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
2005-05-24 7:55 ` [U-Boot-Users] " Benjamin Herrenschmidt
2005-05-24 8:01 ` Segher Boessenkool [this message]
2005-05-24 8:01 ` 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=c7e35bb102646dae463a41a5110d5dfa@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 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.