linux-kernel - Re: [PATCH] Open Firmware device tree virtual filesystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061231.024917.59652177.davem@davemloft.net>
Date:	Sun, 31 Dec 2006 02:49:17 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	dmk@...x.com
Cc:	wmb@...mworks.com, devel@...top.org, linux-kernel@...r.kernel.org,
	jg@...top.org
Subject: Re: [PATCH] Open Firmware device tree virtual filesystem

From: David Kahn <dmk@...x.com>
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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/