Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 May 2009 01:04:39 +0400
From:      Stanislav Sedov <stas@FreeBSD.org>
To:        Guillaume Ballet <gballet@gmail.com>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: LMA != VMA when compiling a kernel
Message-ID:  <20090522010439.1ae3d8c1.stas@FreeBSD.org>
In-Reply-To: <fd183dc60905211318v67d77378t4100f3a0035124ed@mail.gmail.com>
References:  <fd183dc60905211318v67d77378t4100f3a0035124ed@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 21 May 2009 22:18:11 +0200
Guillaume Ballet <gballet@gmail.com> mentioned:

> Hello list,
> 
> I am still working on a port of FreeBSD to the beagleboard, and am
> currently working on enabling the VM. So far, I have loaded the kernel
> at phys_addr = virt_addr = 0x80000000, because that is where the RAM
> is. However, when enabling the VM, I would like the kernel virtual
> addresses to start with 0xC0000000 as they do on most other platform.
> 
> Hence, I have been trying to set the ELF file sections' VMAs to
> something starting with 0xC and the LMAs to something starting with
> 0x8. It turns out that just setting KERNPHYSADDR and KERNVIRTADDR is
> not enough >.< If found a way to do this by chaning the script linker
> and adding AT after each section declaration, and it works fine. But
> it's tedious, hacky and lots of hardcoded values only work with my
> platform.
> 

Does beagleboard use PXA cpu? I know only one place where the physical
memory location for PXA is hardcoded, and I belive it should work fine
after changing it...

- -- 
Stanislav Sedov
ST4096-RIPE
-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAkoVwe0ACgkQK/VZk+smlYEfZgCfdTzYvcyQhghzClcHkXV3ccI7
8JwAn36Gw/pkJVS+jPEM3MiUiSqRKrOE
=hWi6
-----END PGP SIGNATURE-----

!DSPAM:4a15c1c6994291674276043!





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090522010439.1ae3d8c1.stas>