Kumar Gala wrote:
> On Fri, 26 Oct 2007, Scott Wood wrote:
>
>> Scott Wood wrote:
>>> On Fri, Oct 26, 2007 at 10:04:19AM -0500, Kumar Gala wrote:
The reason you have 192M is that lowmem is the total amount of memory
that can be covered by up to three CAM entries. In the case of setting
On Fri, 26 Oct 2007, Scott Wood wrote:
> Scott Wood wrote:
> > On Fri, Oct 26, 2007 at 10:04:19AM -0500, Kumar Gala wrote:
> > > The reason you have 192M is that lowmem is the total amount of memory
> > > that can be covered by up to three CAM entries. In the case of setting
> > > mem=252M that
Scott Wood wrote:
> On Fri, Oct 26, 2007 at 10:04:19AM -0500, Kumar Gala wrote:
>> The reason you have 192M is that lowmem is the total amount of memory
>> that can be covered by up to three CAM entries. In the case of
>> setting mem=252M that max that three CAM entries can cover is 192M (64
On Fri, Oct 26, 2007 at 10:04:19AM -0500, Kumar Gala wrote:
>
> On Oct 25, 2007, at 10:51 PM, Surya Ravikiran wrote:
>
> > Hi,
> >
> > I am trying to bootup a Linux kernel, on a FS eval board with 256M.
> > I pass the kernel argument mem=252M, and see that the kernel boots up
> > fine, but with m
On Oct 25, 2007, at 10:51 PM, Surya Ravikiran wrote:
> Hi,
>
> I am trying to bootup a Linux kernel, on a FS eval board with 256M.
> I pass the kernel argument mem=252M, and see that the kernel boots up
> fine, but with much less memory, ~192M (the closes 64M multiple), and
> I browsed through th
