Date: Thu, 10 Mar 2011 08:41:08 +0530 From: "Jayachandran C." <c.jayachandran@gmail.com> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-mips@freebsd.org Subject: Re: What to do when redboot lies about RAM? Message-ID: <AANLkTimK4s82hSzenLCh40LQZHptb%2BHiJ%2BDJpYBE8bJ2@mail.gmail.com> In-Reply-To: <AANLkTik4yE1RDg7TTNxgph4m2EimRcpLY=EG=ZTc%2BVbc@mail.gmail.com> References: <AANLkTik4yE1RDg7TTNxgph4m2EimRcpLY=EG=ZTc%2BVbc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 10, 2011 at 8:13 AM, Adrian Chadd <adrian@freebsd.org> wrote: > One of the Ubiquiti boards (LS-SR71) has redboot firmware that seems to lie > about the amount of RAM it has. > > Although the board has 32 megabytes of RAM, Redboot only reports 16mb. Linux > doesn't query redboot; it probes the amount of RAM by writing bits and > reading them back until it finds where that fails. > > I've whacked together a quick hack to make this memory selection overridable > in the kernel configuration. > What would be the cleaner way? :) Sibyte (mips/sibyte/sb_machdep.c) has a tunable hw.physmem for this. That has an advantage that you do not have to re-compile the kernel to change the memory setting. There is also a MAXMEM option already in conf/options.mips which can be used I think... JC.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimK4s82hSzenLCh40LQZHptb%2BHiJ%2BDJpYBE8bJ2>