Date: Tue, 02 Jan 2007 14:10:10 -0800 (PST)
Message-Id: <20070102.141010.78710062.davem@davemloft.net>
To: segher@kernel.crashing.org
Cc: benh@kernel.crashing.org, linux-kernel@vger.kernel.org, devel@laptop.org,
       dmk@flex.com, wmb@firmworks.com, jg@laptop.org
Subject: Re: [PATCH] Open Firmware device tree virtual filesystem
From: David Miller <davem@davemloft.net>
In-Reply-To: <578a242271c65db1cf8d85e943fab67a@kernel.crashing.org>
References: <bb0d56f649449edb8b5cc0e1c12ede29@kernel.crashing.org>
	<1167773556.6165.79.camel@localhost.localdomain>
	<578a242271c65db1cf8d85e943fab67a@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: 1088
Lines: 27

From: Segher Boessenkool <segher@kernel.crashing.org>
Date: Tue, 2 Jan 2007 22:40:17 +0100

> >> The kernel doesn't care if one CPU is in OF land while the others
> >> are doing other stuff -- well you have to make sure the OF won't
> >> try to use a hardware device at the same time as the kernel, true.
> >
> > That statement alone hides an absolute can of worms btw ;-)
> 
> Oh I know.  With a sane OF implementation, things will work
> out fine though.

Note that on PPC they do not co-exist with the OFW after
the kernel boots up because it's an enormous can of worms
if not downright impossible.

If I didn't need to make certain OFW calls after bootup on
sparc I'd throw away the OFW mappings and image too.

With software replaced TLBs it's an enormous hassle to
coexist safely with the OFW image.  The locking is a
second order issue.
-
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/