linux-mips
[Top] [All Lists]

Re: early_ioremap for MIPS

To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: early_ioremap for MIPS
From: Ralf Baechle <ralf@linux-mips.org>
Date: Fri, 8 Feb 2008 14:44:17 +0000
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>, Florian Fainelli <florian.fainelli@telecomint.eu>, linux-mips@linux-mips.org
In-reply-to: <20080208122858.GA8267@alpha.franken.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <200802071932.23965.florian.fainelli@telecomint.eu> <Pine.LNX.4.64N.0802081058350.7017@blysk.ds.pg.gda.pl> <20080208122858.GA8267@alpha.franken.de>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.17 (2007-11-01)
On Fri, Feb 08, 2008 at 01:28:59PM +0100, Thomas Bogendoerfer wrote:

> Jazz has the same problem. Right now it's solved by using wired tlb
> entries. Which is sort of an early_ioremap.

One with a totally awkward API requiring the user having to know about
the underlying TLB organization.  A better implementation wouldn't be
hard to do, for anything that's outside of KSEG1's address range grab
a new TLB entry if needed and wire an entry into it.  Use the same
API as good old ioremap() and call the result early_ioremap().

  Ralf

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