linux-mips
[Top] [All Lists]

Re: RFC: [MIPS] BCM1480/BCM1480HT remove io_offset

To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: RFC: [MIPS] BCM1480/BCM1480HT remove io_offset
From: Ralf Baechle <ralf@linux-mips.org>
Date: Thu, 25 Feb 2010 15:05:22 +0100
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>, linux-mips@linux-mips.org
In-reply-to: <1267069502.8811.7.camel@dc7800.home>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <201002241338.41501.bjorn.helgaas@hp.com> <20100224221053.GB20280@alpha.franken.de> <201002241630.42987.bjorn.helgaas@hp.com> <1267069502.8811.7.camel@dc7800.home>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.20 (2009-08-17)
On Wed, Feb 24, 2010 at 08:45:02PM -0700, Bjorn Helgaas wrote:

> Actually, you should be able to make this work with CPU I/O resources of
> your choice even if you can't control the translation.  It just requires
> a little more indirection, like most computer science problems :-)  On
> ia64, we map multiple I/O port spaces with arbitrary translations into a
> 0xSPPPPPP scheme (S = space number, PPPPPP = port number).
> 
> But my main concern is just making sure that my IORESOURCE_PCI_FIXED
> change didn't break BCM1480, and I don't think it will.

The whole IORESOURCE_PCI_FIXED thing was created for Cobalt only and is
needed due to the discontinuity of the port address space with legacy I/O
ports in the range of 0..0x1000 and the rest starting off from 0x10000000.
No other system has such a lobotomized system controller.

  Ralf

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