Date: Thu, 5 Apr 2007 20:55:53 +1200 From: Andrew Turner <andrew@fubar.geek.nz> To: grehan@freebsd.org Cc: freebsd-ppc@freebsd.org Subject: Re: Exception in openfirmware calling Message-ID: <20070405205553.4245f497@hermies.int.fubar.geek.nz> In-Reply-To: <4612EE60.8040103@freebsd.org> References: <20070331141428.5f7cb6b4@hermies.int.fubar.geek.nz> <4612AA47.4060802@freebsd.org> <20070404081638.536ca636@hermies.int.fubar.geek.nz> <4612EE60.8040103@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 03 Apr 2007 17:16:32 -0700 Peter Grehan <grehan@freebsd.org> wrote: > > I've used the ofw_stack code from NetBSD for now. It creates a new > > stack with a real address. > > That will work, though I don't like the way it's implemented: the > calls in all of the OFW routines is a little ugly. My plan was to > have a call_onstack() routine that would allow a function to be > executed on a specified stack. This can be used in other places too, > such as when the initial thread has to switch over to it's allocated > stack. I've managed to use it to get to the point when FreeBSD complains there is no network devices to mount root from. The OF_read and OF_write calls need the ofw_stack. I also allocated a page of real memory that I copy the string to display to in OF_write and read the input data from in OF_read. It is not the best fix but it does allow me to work on other parts of the kernel. Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070405205553.4245f497>