[PATCHv2] staging: tidspbridge: configure full L1 MMU range
Ramirez Luna, Omar
omar.ramirez at ti.com
Fri Jan 14 01:39:19 UTC 2011
On Wed, Jan 5, 2011 at 3:25 PM, Fernando Guzman Lugo
<fernando.lugo at ti.com> wrote:
> From: Guzman Lugo, Fernando <fernando.lugo at ti.com>
> IVA MMU can manage up to 4GB of address space through its page tables,
> given that it's L1 is divided into 1MB sections it requires at least
> 16KB for its table which represents 4096 entries of 32 bits each.
> Previously, only 1GB was being handled by setting the page table size
> to 4KB, any virtual address beyond of the L1 size used, would fall
> into memory that does not belong to L1 translation tables, leading to
> unpredictable results.
> So, set the L1 table size to cover the entire MMU range (4GB) whether
> is meant to be used or not.
> Reported-by: Felipe Contreras <felipe.contreras at nokia.com>
> Signed-off-by: Fernando Guzman Lugo <fernando.lugo at ti.com>
> Signed-off-by: Felipe Contreras <felipe.contreras at nokia.com>
Nice fix, pushed to for-gkh-2.6.38 branch.
More information about the devel