Hi Gavin,
Gavin Lambert wrote:
Quoth Greg Ungerer [EMAIL PROTECTED]:
In modern 2.6 version kernels the RAM mapping is configurable
at "make config" for at least m68k/coldfire and arm, maybe
others too. In older 2.4 kernels it was often hard coded into
platform specific code for that board support.
Not all of it is configurable in 2.6 -- there is still the
aforementioned page_offset.h header file (at least in older versions of
the kernel;
Nope. I fixed this, in modern versions of 2.6 kernels,
page_offset.h now uses the configurable CONFIG_RAMBASE
as the base of physical RAM.
(Ofcourse we are talking m68k/ColdFire here, it varies for
other architectures).
I haven't looked at the recent ones yet). And head.S
definitely has some say in it,
Nope, it doesn't either. It uses the configurable option
CONFIG_RAMSIZE. And for the majority of ColdFire targets
this is set to auto-probe RAMSIZE. Though you can override
that and hard set the RAM size.
Similarly the linker script relies on these configurable
options and CONFIG_KERNELBASE to do all its work.
although I think most of that *is*
overridable by the config.
It is not completely configurable at "config" time.
See the options in arch/m68knommu/Kconfig in the
"RAM configuration" section.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: [EMAIL PROTECTED]
Secure Computing Corporation PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
