From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Olaf Hering <olh@suse.de>, Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/3] openfirmware: adds sysfs nodes for openfirmware devices
Date: Sun, 13 Mar 2005 16:17:19 +0100 [thread overview]
Message-ID: <b34edd09a60d945f41bbe123a8321f22@kernel.crashing.org> (raw)
In-Reply-To: <42277ED8.6050500@suse.com>
Sorry to follow up this late...
>>> Is whitespace (in any form) allowed in the compatible value?
No. Only printable characters are allowed, that is, byte values
0x21..0x7e and 0xa1..0xfe; each text string is terminated by a
0x00; there can be several text strings concatenated in one
"compatible" property.
>> Yes, whitespace is used at least in the toplevel compatible file, like
>> 'Power Macintosh' in some Pismo models.
So those OF implementations violate the OF specification.
> Oh well, it was wishful thinking anyway. ;)
>
> I see two potential solutions:
> * Ideally, I'd like to find a character (pipe?) that isn't used in the
> Apple OF compatible property. I've been unable to find any
> documentation that specifies to this level of detail. (Well, without
> paying for the IEEE-1275 reference, and it may not even be there.)
See 2.3.75 and 3.2.2.1.2 in the OF spec.
Segher
next prev parent reply other threads:[~2005-03-14 13:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 21:18 [PATCH 2/3] openfirmware: adds sysfs nodes for openfirmware devices Jeffrey Mahoney
2005-03-02 23:32 ` Benjamin Herrenschmidt
2005-03-03 18:19 ` Jeff Mahoney
2005-03-03 20:23 ` Olaf Hering
2005-03-03 21:17 ` Jeff Mahoney
2005-03-04 11:02 ` Olaf Hering
2005-03-04 16:35 ` Jeff Mahoney
2005-03-13 15:17 ` Segher Boessenkool [this message]
2005-03-14 14:03 ` Benjamin Herrenschmidt
2005-03-14 14:06 ` Olaf Hering
2005-03-14 14:27 ` Segher Boessenkool
2005-03-14 15:04 ` Benjamin Herrenschmidt
2005-03-14 15:19 ` Jeff Mahoney
2005-03-14 15:19 ` Segher Boessenkool
2005-03-14 21:47 ` Benjamin Herrenschmidt
2005-03-03 22:52 ` 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=b34edd09a60d945f41bbe123a8321f22@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=torvalds@osdl.org \
/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.