linux-mips
[Top] [All Lists]

Re: [PATCH][MIPS][1/7] AR7: core support

To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: [PATCH][MIPS][1/7] AR7: core support
From: Ralf Baechle <ralf@linux-mips.org>
Date: Wed, 12 Sep 2007 14:55:06 +0100
Cc: Matteo Croce <technoboy85@gmail.com>, Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org, florian@openwrt.org, nbd@openwrt.org, ejka@imfi.kspu.ru, nico@openwrt.org, openwrt-devel@lists.openwrt.org, akpm@linux-foundation.org
In-reply-to: <20070912112204.GA7197@alpha.franken.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <200709080143.12345.technoboy85@gmail.com> <200709080218.50236.technoboy85@gmail.com> <20070909.024020.61508994.anemo@mba.ocn.ne.jp> <200709120043.43452.technoboy85@gmail.com> <20070912112204.GA7197@alpha.franken.de>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.14 (2007-02-12)
On Wed, Sep 12, 2007 at 01:22:04PM +0200, Thomas Bogendoerfer wrote:

> probably nothing, but having a generic decision whether we need
> a version with j or jr will help other platforms as well. Why make
> AR7 a special case ?

The destination is potencially outside the range of the j instruction.
Which is something that reasonably be expected on other systems as
well.  One scenario for example is having a few k of RAM at phys 0
then the rest starting at 256MB phys.

It's somewhat easier with an ebase register of course but older cores
don't have that.

  Ralf

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