Re: allocating memory during kernel startup

[Michael <macallan%netbsd.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On May 7, 2010, at 5:31 PM, Eduardo Horvath wrote:

> On Fri, 7 May 2010, Michael wrote:
>
> > In fact I did describe it in another mail.
> > And the problem is that macppc sets up its console extremely early.  
> > If I move
> > consinit() after uvm_init() then debugging uvm_init() problems  
> > becomes a lot
> > harder and as I said before, the parts that need uvm to be up and  
> > running are
> > strictly optional, we only need to know wether we can use them or  
> > not.
>
> You could also do what I did on sparc64: early on attach an OFW  
> console
> and replace it with the real console during the device probe.

I think macppc had an OF console at some point ( there's code that  
looks like it ), I have no idea why it hasn't been used at least since  
1.6. I'd almost bet there are different weirdnesses with different  
versions of Apple's OF even with simple character output though.
Either way, the early rasops console works fine and the problem has  
been solved ( pass a flag that tells rasops not to allocate any  
memory ) - I was just looking for something simpler that doesn't need  
changes all over the place.

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBS+SKBspnzkX8Yg2nAQLeaAf/RUkA5tHxdBviGSa8EHg099+ihU9zpbtI
cosP9Guw9NL59r3MbREqbXLMVnZZlW/IuHNS2h/dV2D7X9u1EoXuBrou/aXkUrH3
JhpKn8d3CHUkHRLF7KMJQPH6Q18cfEhhSPGVHZxGaGk6BkwwXtCRqtbOSpOoESD8
KOc/V7k3AuLj4JWFgT6vnCcoUNKARtoQhT9SlNigpoDoMXyXu301dy75xGRlK41y
Z4DqpjhDvQHtXLnFf1lc3SCtypleQiE8OgKRQBEzGH+I9Js1nS6Zi9+40CevdrUw
w7onT7npArbSmwkCZe1adVDEET3jTCRHWhqCc7risrwWR2lR2S1cPA==
=KMEb
-----END PGP SIGNATURE-----