Date: Mon, 01 Jan 2007 15:08:31 -0800 (PST)
Message-Id: <20070101.150831.17863014.davem@davemloft.net>
To: segher@kernel.crashing.org
Cc: linux-kernel@vger.kernel.org, devel@laptop.org, dmk@flex.com,
       wmb@firmworks.com, hch@infradead.org, jg@laptop.org
Subject: Re: [PATCH] Open Firmware device tree virtual filesystem
From: David Miller <davem@davemloft.net>
In-Reply-To: <385664dfd55cfdfb9f9651fc90bf46b0@kernel.crashing.org>
References: <445cb4c27a664491761ce4e219aa0960@kernel.crashing.org>
	<20070101.005714.35017753.davem@davemloft.net>
	<385664dfd55cfdfb9f9651fc90bf46b0@kernel.crashing.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 962
Lines: 25

From: Segher Boessenkool <segher@kernel.crashing.org>
Date: Mon, 1 Jan 2007 18:48:33 +0100

> If you *really* want (the option of) showing things as text
> in the filesystem, you better make it so that there is a
> one-to-one translation back to binary.  For example, what
> does this mean, is it a text string or two bytes:
> 
> 01.02
> 
> Yes you as a user can guess, but scripts can't (reliably).

We have some extensive code in fs/openpromfs/inode.c that
determines whether a property is text or not.  I can't
guarentee it works %100, but it's very context dependant
(only the driver "knows") but it works for all the cases
I've tried.

I really think you're making a mountain out of a mole hill, to be
honest :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/