Re: [PATCH] Open Firmware device tree virtual filesystem
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Date: Sun, 31 Dec 2006 15:41:03 +0000
On Sun, Dec 31, 2006 at 02:49:17AM -0800, David Miller wrote:
From: David Kahn <dmk@xxxxxxxx>
Date: Sun, 31 Dec 2006 02:11:53 -0800
All we've done is created a trivial implementation for exporting
the device tree to userland that isn't burdened by the powerpc
and sparc legacy code that's in there now.
So now we'll have _3_ different implementations of exporting
the OFW device tree via procfs. Your's, the proc_devtree
of powerpc, and sparc's /proc/openprom
That doesn't make any sense to me, having 3 ways of doing the same
exact thing and making no attempt to share code at all.
If you want to do something new that consolidates everything, with the
goal of deprecating the existing stuff, that's great! But with they
way you're doing this, all the sparc and powerpc implementations
really can't take advantage of it.
Am I the only person who sees something very wrong with this?
No, I completely agree with you on this.
If firmworks really wants to have a spearate filesystem that's fine.
But please start with the ppc or sparc code and massage it into a
a separate filesystem before adding support for a new platform.
The last thing we need is more duplication.
In case anyone wants to start this based on ppc I'd gladfully help
to test this on pmac (32 and 64bit) and cell (64 bit).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] Open Firmware device tree virtual filesystem
- From: David Miller
- Re: [PATCH] Open Firmware device tree virtual filesystem
- References:
- Re: [PATCH] Open Firmware device tree virtual filesystem
- From: David Miller
- Re: [PATCH] Open Firmware device tree virtual filesystem
- From: Mitch Bradley
- Re: [PATCH] Open Firmware device tree virtual filesystem
- From: David Kahn
- Re: [PATCH] Open Firmware device tree virtual filesystem
- From: David Miller
- Re: [PATCH] Open Firmware device tree virtual filesystem
- Prev by Date: Re: kref refcnt and false positives
- Next by Date: Re: Suspend problems on 2.6.20-rc2-git1
- Previous by thread: Re: [PATCH] Open Firmware device tree virtual filesystem
- Next by thread: Re: [PATCH] Open Firmware device tree virtual filesystem
- Index(es):
Relevant Pages
- Re: [PATCH] Open Firmware device tree virtual filesystem
... the device tree to userland that isn't burdened by the powerpc ... and
sparc legacy code that's in there now. ... If firmworks really wants to have a spearate
filesystem that's fine. ... (Linux-Kernel) - Re: [PATCH] Open Firmware device tree virtual filesystem
... the device tree to userland that isn't burdened by the powerpc ... and
sparc legacy code that's in there now. ... "exporting the OFW device tree". ...
(Linux-Kernel) - Re: [PATCH] Open Firmware device tree virtual filesystem
... the device tree to userland that isn't burdened by the powerpc ... So
now we'll have _3_ different implementations of exporting ... all of the necessary operations
and allows just about any ... (Linux-Kernel) - Re: [PATCH] Open Firmware device tree virtual filesystem
... the device tree to userland that isn't burdened by the powerpc ... and
sparc legacy code that's in there now. ... So now we'll have _3_ different implementations
of exporting ... (Linux-Kernel) - Re: interrupting for overflow and loop termination
... >> but it turned out to be easier and faster for implementations of Smalltalk
... >> and similar languages to use other tricks that don't require hardware support.
... > 1) There was Berkeley SOAR as noted, and SPARC included ADD/SUB Tagged, ...
adding any significant change in the general purpose ISA, ... (comp.arch)