From: "DPR" <info-IGm5bqYn3xwb1SvskN2V4Q@public.gmane.org>
To: "'Grover,
Andrew'" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"'Cagle,
John (ISS-Houston)'" <john.cagle-VXdhtT5mjnY@public.gmane.org>,
info-IGm5bqYn3xwb1SvskN2V4Q@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: alan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: RE: mpparse.c APIC/ACPI support
Date: Tue, 4 Mar 2003 19:54:10 +0100 [thread overview]
Message-ID: <000001c2e27f$74ae2910$0200a8c0@brutzler> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A1C9-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
> The device's driver calls pci_enable_device, which calls:
> pci_enable_device_bars, which calls:
> pcibios_enable_device, which calls:
> pcibios_enable_irq, which is a function pointer we set to
> acpi_pci_irq_enable, which does an eisa_set_level_irq(), thus setting
> the interrupt (if less than 16) to level-triggered.
>
> So why isn't it working? Hmm.
Perhaps these messages from "pcibios_enable_irq" will help you finding the error ...
<4>PCI: No IRQ known for interrupt pin A of device 00:10.0
<4>PCI: No IRQ known for interrupt pin B of device 00:10.1
<4>PCI: No IRQ known for interrupt pin C of device 00:10.2
<4>PCI: No IRQ known for interrupt pin D of device 00:10.3
<4>PCI: No IRQ known for interrupt pin A of device 00:11.1 - using IRQ 255
<4>PCI: No IRQ known for interrupt pin A of device 00:12.0
The devices 00:10.0 up to 00:10.3 are my USB 1.1/2.0 controllers, device 00:11.1 is my EIDE
controller and device 00:12.0 is my ethernet adapter.
Regards,
HOLGER
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
next prev parent reply other threads:[~2003-03-04 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 18:21 mpparse.c APIC/ACPI support Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84725A1C9-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-03-04 18:54 ` DPR [this message]
[not found] ` <000001c2e27f$74ae2910$0200a8c0-IGm5bqYn3xw@public.gmane.org>
2003-03-04 21:24 ` Alan Cox
2003-03-05 21:51 ` DPR
[not found] ` <000501c2e361$5f21d1e0$0200a8c0-IGm5bqYn3xw@public.gmane.org>
2003-03-05 22:22 ` DPR
-- strict thread matches above, loose matches on Subject: below --
2003-04-18 16:28 Cagle, John (ISS-Houston)
2003-04-18 15:56 Grover, Andrew
2003-04-15 19:53 Cagle, John (ISS-Houston)
2003-04-15 7:41 Cagle, John (ISS-Houston)
2003-04-15 0:31 Grover, Andrew
2003-04-14 23:24 Cagle, John (ISS-Houston)
2003-03-04 17:34 Cagle, John (ISS-Houston)
2003-03-03 17:02 Grover, Andrew
2003-03-02 3:29 Cagle, John (ISS-Houston)
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='000001c2e27f$74ae2910$0200a8c0@brutzler' \
--to=info-igm5bqyn3xwb1svskn2v4q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=alan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=john.cagle-VXdhtT5mjnY@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