On Oct 3, 2007, at 4:45 PM, Rune Torgersen wrote:
>> From: Kumar Gala
>> The code would have to change to allow for 1G of lowmem.
>> Max lowmem with KERNELBASE @ 0xc000_ is 768M.
>
> Which is why I asked. On 82xx it is supported without a codechange by
> setting KERNELBASE to 0xa000_ in K
> From: Kumar Gala
> The code would have to change to allow for 1G of lowmem.
> Max lowmem with KERNELBASE @ 0xc000_ is 768M.
Which is why I asked. On 82xx it is supported without a codechange by
setting KERNELBASE to 0xa000_ in Kconfig menu (and also changing
start of virtual mem, also do
On Oct 3, 2007, at 2:34 PM, Rune Torgersen wrote:
>> From: Dale Farnsworth
>>
>> The CONFIG_FSL_BOOKE mmu setup code fails when CONFIG_HIGHMEM=y
>> and the 3 fixed TLB entries cannot exactly map the lowmem size.
>> Each TLB entry can map 4MB, 16MB, 64MB or 256MB, so the failure
>> is observed whe
On Wed, Oct 03, 2007 at 02:34:42PM -0500, Rune Torgersen wrote:
> > From: Dale Farnsworth
> >
> > The CONFIG_FSL_BOOKE mmu setup code fails when CONFIG_HIGHMEM=y
> > and the 3 fixed TLB entries cannot exactly map the lowmem size.
> > Each TLB entry can map 4MB, 16MB, 64MB or 256MB, so the failure
> From: Dale Farnsworth
>
> The CONFIG_FSL_BOOKE mmu setup code fails when CONFIG_HIGHMEM=y
> and the 3 fixed TLB entries cannot exactly map the lowmem size.
> Each TLB entry can map 4MB, 16MB, 64MB or 256MB, so the failure
> is observed when the kernel lowmem size is not equal to the
> sum of up
From: Dale Farnsworth <[EMAIL PROTECTED]>
The CONFIG_FSL_BOOKE mmu setup code fails when CONFIG_HIGHMEM=y
and the 3 fixed TLB entries cannot exactly map the lowmem size.
Each TLB entry can map 4MB, 16MB, 64MB or 256MB, so the failure
is observed when the kernel lowmem size is not equal to the
sum
