Subject: Re: Issues with /proc/bus/pci
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Paul Mackerras <paulus@samba.org>,
       Linux Kernel list <linux-kernel@vger.kernel.org>
In-Reply-To: <20040322194759.7a38ffe9.davem@redhat.com>
References: <1080007613.22212.61.camel@gaston>
	 <20040322183126.16fe76cc.davem@redhat.com>
	 <1080009609.23717.81.camel@gaston>
	 <20040322194759.7a38ffe9.davem@redhat.com>
Content-Type: text/plain
Message-Id: <1080015161.23717.99.camel@gaston>
Mime-Version: 1.0
Date: Tue, 23 Mar 2004 15:12:41 +1100
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1033
Lines: 28

On Tue, 2004-03-23 at 14:47, David S. Miller wrote:
> On Tue, 23 Mar 2004 13:40:11 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> 
> > What do you think ?
> 
> Ok, it does sound like we need something else.

Ok, finally, I found out the truth about the ppc "fix" for that:
paulus did indeed fix it ... in 2.4 and not 2.5 :( Paul's fix is
simply to have the arch allow mapping of any address that is on
the host resource ranges, whatever the device was passed in (that
is basically the same as considering any device to be the host
bridge).

That should be completely compatible with userland looking for the
host bridge and would let me get the low VGA stuff for my video
softboot hack from the same device fd without having to look for
the host bridge at all.

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/