From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] openfirmware: adds sysfs nodes for openfirmware devices
Date: Fri, 04 Mar 2005 09:52:56 +1100 [thread overview]
Message-ID: <1109890376.5679.236.camel@gaston> (raw)
In-Reply-To: <42275536.8060507@suse.com>
> Reviewing the 'compatible' values in my device-tree, I definately agree.
> I can hack the pmac_zilog driver to test this out further - I've just
> been using my airport card.
>
> Are there any other "invalid" characters for the compatible property?
> CRLF would work, but these values (as a group) need to be put into
> modules.ofmap as well as passed via environment variables for hotplug.
> As such, CRLF isn't really easiest choice to work with.
I don't think any value is "invalid". Not sure what is best to use ...
maybe '#' ? never seen it in there so far ... but who knows ...
> Is whitespace (in any form) allowed in the compatible value?
Yes. For example: "Power Macintosh" is a typical compatible value in the
root of the devive tree.
Maybe "tab" ?
Ben.
prev parent reply other threads:[~2005-03-03 23:16 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
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 [this message]
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=1109890376.5679.236.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox