linux-mips
[Top] [All Lists]

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

To: <mbizon@freebox.fr>
Subject: RE: [PATCH] MIPS: Allocate exception vector on 64 KiB boundary
From: "David VomLehn (dvomlehn)" <dvomlehn@cisco.com>
Date: Fri, 13 Feb 2009 13:41:52 -0500
Authentication-results: rtp-dkim-1; header.From=dvomlehn@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: <linux-mips@linux-mips.org>, <ralf@linux-mips.org>, "David Daney" <ddaney@caviumnetworks.com>
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=1118; t=1234550513; x=1235414513; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dvomlehn@cisco.com; z=From:=20=22David=20VomLehn=20(dvomlehn)=22=20<dvomlehn@cis co.com> |Subject:=20RE=3A=20[PATCH]=20MIPS=3A=20Allocate=20exceptio n=20vector=20on=2064=20KiB=20boundary |Sender:=20 |To:=20<mbizon@freebox.fr>; bh=iWrHvyW+ZEt+AGXGzeM9r4JM8JAegK2p7Xs/gNvvZRU=; b=U7thLNw8nQy4hoOh29tqUIVD0mffy6hg8wyCUDbYkkS7kOWM9NVE1B1Fx1 stB/HnVH1Yz7lAM5pOH0pX8cBAyWUpkJkSZ9XFG2Kkj+dDHltUncwUVhTjwY RFYe+BL3OX;
In-reply-to: <1234532640.711.63.camel@sakura.staff.proxad.net>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <FF038EB85946AA46B18DFEE6E6F8A28982392E@xmb-rtp-218.amer.cisco.com> <1234532640.711.63.camel@sakura.staff.proxad.net>
Sender: linux-mips-bounce@linux-mips.org
Thread-index: AcmN4SwSSf7Q833JSEe/nf8vSv/UKgAKYM+w
Thread-topic: [PATCH] MIPS: Allocate exception vector on 64 KiB boundary
> From: Maxime Bizon [mailto:mbizon@freebox.fr] 
> Sent: Friday, February 13, 2009 5:44 AM
> To: David VomLehn (dvomlehn)
> Cc: linux-mips@linux-mips.org; ralf@linux-mips.org; David Daney
> Subject: Re: [PATCH] MIPS: Allocate exception vector on 64 
> KiB boundary
> 
> 
> 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.

Can you confirm that the patch fixes your problem?

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