From: Dominik Brodowski <devel-JhLEnvuH02M@public.gmane.org>
To: "M. Warner Losh" <imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org>
Cc: joerg.beyer-htSm2yLGOjU@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: not all irqs detected
Date: Sat, 24 Aug 2002 21:00:58 +0200 [thread overview]
Message-ID: <20020824210055.A1252@brodo.de> (raw)
In-Reply-To: <20020824.121703.52419660.imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org>; from imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org on Sat, Aug 24, 2002 at 12:17:03PM -0600
> : > I tried to read & understand the driver/acpi/pci_*.c code, but I need
> : > some help to get started: how are the free/usable IRQs found
> : > and mapped?
>
> Actually, that's not the case ('all shoule be free').
Thanks for clearing that up, I actually meant that all _usable_ IRQs (i.e.
those in the ACPI PRT tables) should be _available_ == free... So it should
be:
| The usable IRQs are set down in the DSDT table, the Detailed System
| Description Table (which is more or less fixed in the BIOS). And as all PCI
| IRQs are expected to be non-exclusive, all of those usable IRQs should be
| available / "free for use". However, the ACPI code tries to use the
| available IRQs most effectively, i.e. no sharing of IRQs if possible.
Dominik
-------------------------------------------------------
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-08-24 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 17:17 not all irqs detected joerg.beyer-htSm2yLGOjU
[not found] ` <200208241717.g7OHH1X19234-pb599fR3TxVkExQqqHjIK3sFFmKitW5W@public.gmane.org>
2002-08-24 18:05 ` Dominik Brodowski
[not found] ` <20020824200511.G587-JhLEnvuH02M@public.gmane.org>
2002-08-24 18:17 ` M. Warner Losh
[not found] ` <20020824.121703.52419660.imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org>
2002-08-24 19:00 ` Dominik Brodowski [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=20020824210055.A1252@brodo.de \
--to=devel-jhlenvuh02m@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org \
--cc=joerg.beyer-htSm2yLGOjU@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