linux-mips
[Top] [All Lists]

Re: early_ioremap for MIPS

To: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: early_ioremap for MIPS
From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
Date: Fri, 8 Feb 2008 13:28:59 +0100
Cc: Florian Fainelli <florian.fainelli@telecomint.eu>, linux-mips@linux-mips.org
In-reply-to: <Pine.LNX.4.64N.0802081058350.7017@blysk.ds.pg.gda.pl>
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>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.13 (2006-08-11)
On Fri, Feb 08, 2008 at 11:05:12AM +0000, Maciej W. Rozycki wrote:
> On Thu, 7 Feb 2008, Florian Fainelli wrote:
> 
> > Is there any need for early_ioremap on MIPS ? Seems like only x86_64 is 
> > implementing it for now.
> 
> physical address space could potentially benefit though.  I recall some 
> Alchemy systems may fall into this category.

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

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                                [ RFC1925, 2.3 ]

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