Date: Mon, 4 Mar 2013 21:30:01 -0700 From: Warner Losh <imp@bsdimp.com> To: Ian Lepore <ian@FreeBSD.org> Cc: freebsd-arm@FreeBSD.org Subject: Re: GENERIC kernel issues Message-ID: <3DFABC9A-876A-4F34-9E15-E4C630D7B077@bsdimp.com> In-Reply-To: <1362445777.1195.299.camel@revolution.hippie.lan> References: <DF7B73D4-BE50-4E75-8D5B-FE19A4764F31@freebsd.org> <1362445777.1195.299.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 4, 2013, at 6:09 PM, Ian Lepore wrote: > On Sun, 2013-03-03 at 11:43 -0800, Tim Kientzle wrote: >>=20 >> ** PHYSADDR/KERNPHYSADDR hardwiring. Ian has made a >> lot of progress and I'm working on some related changes to >> address this. I think we understand how to eliminate these >> constants and replace them with run-time detection of the >> load address. I'm still not sure what changes might be needed >> to the loader to make this work.=20 >=20 > I don't think anything more needs to be done to the loader to be able = to > load a kernel built with the ldscript changes, beyond the change I did = a > week or two ago to make it work right with elf headers that contain > physical addresses. >=20 > On the other hand, I haven't got anything to offer on the problem of = the > loader needing to be linked differently for each board or SoC, since > they all have physical memory in differing address ranges. Well, the Phyiscal memory load address is just a hint after all. Any way = to leave it blank and have ubldr cope by putting it in the first = available phyiscal memory slot from the FDT? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DFABC9A-876A-4F34-9E15-E4C630D7B077>