As reported by Artyom Tarasenko, kadb on some versions of Solaris seems to assume that it can freely make use of memory below the ROM image.
Hence move the dynamic virtual memory allocation range lower in memory (beneath the ROM image and DVMA area) so that kadb can run.
Signed-off-by: Mark Cave-Ayland mark.cave-ayland@ilande.co.uk --- openbios-devel/arch/sparc32/ofmem_sparc32.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/openbios-devel/arch/sparc32/ofmem_sparc32.c b/openbios-devel/arch/sparc32/ofmem_sparc32.c index a6557df..8a81829 100644 --- a/openbios-devel/arch/sparc32/ofmem_sparc32.c +++ b/openbios-devel/arch/sparc32/ofmem_sparc32.c @@ -61,7 +61,8 @@ ucell ofmem_arch_get_heap_top(void)
ucell ofmem_arch_get_virt_top(void) { - return (ucell)TOP_OF_RAM; + /* Return the highest address beneath the ROM image and DVMA area */ + return (ucell)0xfe000000; }
phys_addr_t ofmem_arch_get_phys_top(void)