From: Sven Luther <sven.luther@wanadoo.fr>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Rob Baxter <robb@synergymicro.com>,
Sven Luther <sven.luther@wanadoo.fr>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: multiple separate pci bridges ...
Date: Tue, 13 Jan 2004 10:56:38 +0100 [thread overview]
Message-ID: <20040113095638.GA7633@iliana> (raw)
In-Reply-To: <1073425055.784.3.camel@gaston>
On Wed, Jan 07, 2004 at 08:37:36AM +1100, Benjamin Herrenschmidt wrote:
>
> > Here's the code from our pcibios_fixup:
> >
> > dev = NULL;
> > while ((dev = pci_find_device(PCI_VENDOR_ID_GALILEO,
> > PCI_DEVICE_ID_GALILEO_GT64260, dev))) {
> > for (i = 0; i < DEVICE_COUNT_RESOURCE; i++) {
> > dev->resource[i].flags = 0;
> > dev->resource[i].start = 0;
> > dev->resource[i].end = 0;
> > }
> > }
>
> pcibios_fixup isn't the right place to do that ;) You should do this
> from a pci quirk imho.
Mmm, what do you mean by a pci quirk ?
Anyway, i did that from pcibios_fixup, as well as blocking all pci
writes to device 0 on both buses and reads to all functions of device 0
on both bus, except function 0, for which i allow reads of the first 15
bytes, and return 0 for the others, as i am told i should do by the
hardware guys.
This works fine for the fbdev, but X is not at all happy with it, well,
it seems to work, but there is nothing outputed on the screen :(, but
that is something i probably have to solve with XFree86.
> note that there's still a problem with XFree which will "see" those
> BARs and, according to the log posted by Sven, shoke. Sven, can you
> try "hiding" the host bridge completely from the config ops and see
> if that helps with XFree ? That's not a very good solution though,
> we'll have to do something different about it. Now if only XFree
> stopped mucking with the PCI bus...
So, yes, that does help with XFree86, altough i get a strange message i
have to search the origin for :
(WW) ****INVALID IO ALLOCATION**** b: 0x1000 e:0x10ff correcting
Also, with voodoo 3 cards, the tdfx driver dies with :
(EE) TDFX(0): No valid PIO address in PCI config space
But Radeon works.
Friendly,
Sven Luther
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-13 9:56 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 18:11 multiple separate pci bridges Sven Luther
2004-01-02 4:03 ` Benjamin Herrenschmidt
2004-01-02 7:40 ` Sven Luther
2004-01-02 7:49 ` Benjamin Herrenschmidt
2004-01-04 21:03 ` Sven Luther
2004-01-04 21:45 ` Benjamin Herrenschmidt
2004-01-04 22:06 ` Sven Luther
2004-01-05 16:40 ` Sven Luther
2004-01-05 21:28 ` Benjamin Herrenschmidt
2004-01-05 21:42 ` Sven Luther
2004-01-05 22:12 ` Benjamin Herrenschmidt
2004-01-06 7:39 ` Sven Luther
2004-01-06 8:00 ` Benjamin Herrenschmidt
2004-01-06 8:11 ` Sven Luther
2004-01-06 14:40 ` Geert Uytterhoeven
2004-01-06 14:45 ` Sven Luther
2004-01-06 15:33 ` Rob Baxter
2004-01-06 17:44 ` Sven Luther
2004-01-06 21:37 ` Benjamin Herrenschmidt
2004-01-06 22:10 ` Marcus Barrow
2004-01-06 22:17 ` Rob Baxter
2004-01-06 22:31 ` Benjamin Herrenschmidt
2004-01-07 2:35 ` Sven Luther
2004-01-07 2:36 ` Benjamin Herrenschmidt
2004-01-07 2:40 ` Sven Luther
2004-01-07 9:02 ` Michael Schmitz
2004-01-07 9:23 ` Benjamin Herrenschmidt
2004-01-07 9:56 ` Sven Luther
2004-01-07 10:27 ` Michael Schmitz
2004-01-13 9:56 ` Sven Luther [this message]
2004-01-13 10:26 ` Sven Luther
2004-01-18 12:15 ` Sven Luther
2004-01-18 13:00 ` Michel Dänzer
2004-01-18 13:14 ` Sven Luther
2004-01-19 9:12 ` Benjamin Herrenschmidt
2004-01-18 22:27 ` Sven Luther
2004-01-18 22:59 ` Benjamin Herrenschmidt
2004-01-19 9:21 ` Sven Luther
2004-01-18 23:24 ` Benjamin Herrenschmidt
2004-01-05 21:38 ` Marcus Barrow
2004-01-06 7:14 ` Sven Luther
2004-01-06 7:56 ` Benjamin Herrenschmidt
2004-01-06 8:20 ` Sven Luther
2004-01-02 18:34 ` Geert Uytterhoeven
2004-01-02 15:18 ` Rob Baxter
2004-01-02 23:56 ` Benjamin Herrenschmidt
2004-01-03 0:27 ` Rob Baxter
2004-01-03 1:12 ` Benjamin Herrenschmidt
2004-01-05 0:52 ` Rob Baxter
2004-01-05 2:13 ` Benjamin Herrenschmidt
2004-01-06 20:53 Marcus Barrow
2004-01-06 21:09 Marcus Barrow
2004-01-06 22:59 ` Benjamin Herrenschmidt
2004-01-06 23:00 ` Benjamin Herrenschmidt
2004-01-18 14:44 Sven Luther
2004-01-18 16:33 ` Michel Dänzer
2004-01-18 17:28 ` Sven Luther
2004-01-18 18:24 ` Michel Dänzer
2004-01-18 22:20 ` Sven Luther
2004-01-18 23:33 ` Michel Dänzer
2004-01-19 9:55 ` Sven Luther
2004-01-19 13:48 ` Sven Luther
2004-01-19 13:54 ` Geert Uytterhoeven
2004-01-19 14:00 ` Sven Luther
2004-01-19 14:02 ` Michel Dänzer
2004-01-19 14:16 ` Sven Luther
2004-01-19 14:31 ` Michel Dänzer
2004-01-19 9:11 ` Benjamin Herrenschmidt
2004-01-18 22:33 ` Sven Luther
2004-01-18 23:23 ` Michel Dänzer
2004-01-18 23:42 ` Benjamin Herrenschmidt
2004-01-19 0:03 ` Michel Dänzer
2004-01-19 10:08 ` Geert Uytterhoeven
2004-01-19 11:41 ` Benjamin Herrenschmidt
2004-01-19 12:03 ` Sven Luther
2004-01-19 21:35 ` Benjamin Herrenschmidt
2004-01-19 22:08 ` Sven Luther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040113095638.GA7633@iliana \
--to=sven.luther@wanadoo.fr \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=robb@synergymicro.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.