From: John M Trostel <jtrostel-mn4gwa5WIIQysxA8WJXlww@public.gmane.org>
To: Patrick Mochel <mochel-3NddpPZAyC0@public.gmane.org>
Cc: ACPI-list <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: Can't Find PCI: primary perr bus 01 with ACPI on
Date: Mon, 09 Sep 2002 12:58:37 -0400 [thread overview]
Message-ID: <1031590718.1942.1.camel@jtsdell> (raw)
In-Reply-To: <Pine.LNX.4.44.0209071328300.1021-100000-yZQdDDOm3n9ZQn2sFP3R7eTW4wlIGRCZ@public.gmane.org>
The phrase I am not seeing is:
"PCI: Discovered primary peer bus 01 [IRQ]"
That appears to be coming from pirq_peer_trick in pci_irq.c
None of which is ACPI, but it sure doesn't show up when ACPI is
enabled. Any other clues?
On Sat, 2002-09-07 at 16:30, Patrick Mochel wrote:
>
> On Fri, 6 Sep 2002 jtrostel-mn4gwa5WIIQysxA8WJXlww@public.gmane.org wrote:
>
> > I'm using 2.4.19... with patches from Sergio Basto at http://codecs.home.sapo.pt/acpi/
>
> For some reason, pci_fixup_peer_bridges() is not getting called.
>
> Since it's 2.4.x, I'm ignorant as to why and to what the code looks like,
> and I would like to remain in my state of bliss. So, I'm deferring it.
> Sorry...
>
>
> -pat
--
John M. Trostel
Atlanta GA USA
jtrostel-mn4gwa5WIIQysxA8WJXlww@public.gmane.org
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
prev parent reply other threads:[~2002-09-09 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-07 0:26 Re: Can't Find PCI: primary perr bus 01 with ACPI on jtrostel-mn4gwa5WIIQysxA8WJXlww
[not found] ` <E17nTRe-0002pN-00-d6NqQtMd5t6HWO7mcI6GbnHfL+gkQO6L@public.gmane.org>
2002-09-07 20:30 ` Patrick Mochel
[not found] ` <Pine.LNX.4.44.0209071328300.1021-100000-yZQdDDOm3n9ZQn2sFP3R7eTW4wlIGRCZ@public.gmane.org>
2002-09-09 16:58 ` John M Trostel [this message]
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=1031590718.1942.1.camel@jtsdell \
--to=jtrostel-mn4gwa5wiiqysxa8wjxlww@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mochel-3NddpPZAyC0@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox