> Now that hack took longer to implement than a proper solution ...
Yeah, that hack did take longer to implement than a proper solution. But
it was what I could come up with at the time, as I haven't gone digging
that far down into the kernel sources yet (and unfortunately, the prom.c
source wasn't very helpful either.
> > that would be useful to work past the memory hole?
> Put something like the following into your systems prom_meminit:
> add_memory_region(0UL , 16UL << 20, BOOT_MEM_RAM);
> add_memory_region(16UL , 16UL << 20, BOOT_MEM_RESERVED);
> add_memory_region(32UL << 20, 32UL << 20, BOOT_MEM_RAM);
> You may want to account for additional memory areas and do a proper detection
> etc., exclude area which are used by the firmware etc.
I'm pretty sure that 16M region in the 16-32M area is unused: it's
possible to solder another 2 8M dram chips on the board and increase the
memory to 64M..
Thanks for the help. :)