linux-mips
[Top] [All Lists]

Re: [PATCH] MIPS: Allocate exception vector on 64 KiB boundary

To: "David VomLehn (dvomlehn)" <dvomlehn@cisco.com>
Subject: Re: [PATCH] MIPS: Allocate exception vector on 64 KiB boundary
From: Maxime Bizon <mbizon@freebox.fr>
Date: Fri, 13 Feb 2009 14:44:00 +0100
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org, David Daney <ddaney@caviumnetworks.com>
In-reply-to: <FF038EB85946AA46B18DFEE6E6F8A28982392E@xmb-rtp-218.amer.cisco.com>
Organization: Freebox
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <FF038EB85946AA46B18DFEE6E6F8A28982392E@xmb-rtp-218.amer.cisco.com>
Reply-to: mbizon@freebox.fr
Sender: linux-mips-bounce@linux-mips.org
On Fri, 2009-01-30 at 13:43 -0500, David VomLehn (dvomlehn) wrote:

> Fix problem with code that incorrectly modifies ebase.
> 
> Commit 566f74f6b2f8b85d5b8d6caaf97e5672cecd3e3e had a change that
> incorrectly
> modified ebase. This backs out the lines that modified ebase and then
> modified

I confirm this commit prevents my 4kec board from booting.

My c0_ebase is set to 0x90000000.

In trap_init() ebase is first set to CAC_BASE => 0x80000000, then
0x90000000 after adding c0_ebase offset.

set_uncached_handler() starts with uncached_ebase sets to
KSEG1ADDR(ebase) => 0xb0000000, which is already the correct value, but
it then add the c0_ebase offset again => 0xc0000000 => boom.

-- 
Maxime



<Prev in Thread] Current Thread [Next in Thread>