Subject: Re: Bootloader TODO list
To: Chris Gilbert <chris@paradox.demon.co.uk>
From: Reinoud Zandijk <imago@kabel065011.kabel.utwente.nl>
List: port-arm32
Date: 02/05/2001 18:10:50
Hi Chris,

On Mon, 5 Feb 2001, Reinoud Zandijk wrote:
> > Well it works, but the vidc seems to go horribly wrong when booting, eg the 
> > awful noise and the mouse pointer going to pot, thinking about it it could be 
> > the way that I've got the VM arranged on my code.  I suppose that any changes 
> > to the VM layout need to be reflected back to the bootloader.  Much as the 
> > old bootloader had it's quirks, pretty much the first thing it did was sort 
> > out it's Page tables so that things were in the right place.
> 
> Nope, thats not nessisary. The mouse pointer gets freaked out for its
> memory dissapears and i think the screen just squeeks for it needs to be
> reinitialised on the new position .... during the relocation process the
> VIDC is displaying from (non existent?) memory (well I guess from the 1Mb
> VRAM) but the RAM isnt mapped where it's expecting it.... that might give
> the squeeky noise... one of the first things the new bootloader does it to
> set up the screen to a valid address etc... maybe i can tweek in the
> screenblanker or so ... hmm... nah i think that would give the same
> squeeking and i dont like the idea really to have dedicated VIDC stuff in
> the bootloader really.... its not allways there and doesnt have to be on
> the same place either !!!

Please forget this gibberish from me !!! I must have been sleep-walking
hehe... the virtual memory map ofcource only lives in the ARM processors
view of the memory map ... ahum !!

The problems with the VIDC however are more likely to be with the build
system .... have you tried rebuilding from scratch ? that might solve some
problems... i've had this before too...

The fact that the mouse pointer gets screwed up is nothing to worry about.
It is programmed to use a block on a designated piece of DRAM. This piece
of DRAM is now however used for something else... f.e. the kernel and so
it displays a bit of kernel code until its reinitialised :)) ... thats
all....

You do run the kernel in a non 800x600 mode with 256 colours do you? The
current vidcconsole code requires that... just as the old one. Running in
1024x786 in 256 colours should be fine.

Cheers,
Reinoud