Re: [PATCH] Open Firmware device tree virtual filesystem
- From: David Kahn <dmk@xxxxxxxx>
- Date: Sun, 31 Dec 2006 03:53:06 -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
I would not exactly call what we have for powerpc
"exporting the OFW device tree". I don't quite know
what it is, but it isn't as simple as exporting the
OFW device tree. I don't think we really wanted to
get into any of that here.
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.
Sure they can take advantage of it, if what they need
to export is a read-only copy of the actual device tree
without any legacy burden or having a writable/changeable
copy of it with a trivial implementation. But that's not
up to us, and that's not what's been done for powerpc and
sparc.
This is a trivial implementation that suits it's purpose.
It's simple. I'm not sure what more is needed for this
project when it's pretty clear that i386 will never need
any additional support for open firmware.
-David
-
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/
- 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: [PATCH 2.6.19] mmc: Add support for SDHC cards
- Next by Date: Re: ipw2200 device naming problems in 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. ... So now we'll have _3_ different implementations
of exporting ... (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. ... If firmworks really wants to have a spearate
filesystem that's fine. ... (Linux-Kernel) - Re: [PATCH] Open Firmware device tree virtual filesystem
... PowerPC only for a while, until everything is converted -- SPARC ... The sole
exception ... one with a global invalidate on any device tree ... Does any generic
such cache for all ... (Linux-Kernel) - Re: [PATCH] Open Firmware device tree virtual filesystem
... This patch creates a virtual filesystem that represents an Open Firmware ...
create a flattened representation of the device tree. ... On sparc and powerpc,
we even build an in-kernel data structure of the ... (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)