* mips_memory_upper
@ 2001-04-09 13:38 Scott A McConnell
2001-04-09 14:15 ` mips_memory_upper Maciej W. Rozycki
0 siblings, 1 reply; 2+ messages in thread
From: Scott A McConnell @ 2001-04-09 13:38 UTC (permalink / raw)
To: linux-mips
Used to be defined in ./arch/mips/kernel/setup.c
It is no longer defined. I also noticed that badget is now using
vac_memory_upper.
Can anyone fill me in on the details.
Thanks,
Scott
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: mips_memory_upper
2001-04-09 13:38 mips_memory_upper Scott A McConnell
@ 2001-04-09 14:15 ` Maciej W. Rozycki
0 siblings, 0 replies; 2+ messages in thread
From: Maciej W. Rozycki @ 2001-04-09 14:15 UTC (permalink / raw)
To: Scott A McConnell; +Cc: linux-mips
On Mon, 9 Apr 2001, Scott A McConnell wrote:
> Used to be defined in ./arch/mips/kernel/setup.c
It's no longer needed -- MIPS now uses the bootmem allocator cosistently
across system variations. Memory holes are now permitted. User may
override the determined memory map using a kernel command line (for
debugging, to isolate a faulty module, etc.). The add_memory_region()
function is used to register an area of memory.
> It is no longer defined. I also noticed that badget is now using
> vac_memory_upper.
This is a system-specific value to write into chipset registers. It's
not overriden by a kernel command line in any case to initialize the
chipset properly. I can't say anything more specific about it -- I'm not
a Baget expert.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-04-09 14:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-04-09 13:38 mips_memory_upper Scott A McConnell
2001-04-09 14:15 ` mips_memory_upper Maciej W. Rozycki
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox