public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Li,
	Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [nico-kernel-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org: [BUG] pdc202xx_new and ACPI fails]
Date: Tue, 7 Dec 2004 18:35:32 +0100	[thread overview]
Message-ID: <20041207173531.GA2289@schottelius.org> (raw)
In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575B640E1-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org> <F7DC2337C7631D4386A2DF6E8FB22B30022F857C-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org> <1102286168.2308.13.camel@d845pe>

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

Li, Shaohua [Tue, Dec 07, 2004 at 03:13:36PM +0800]:
> Yes, it should print something. Very strange. Let us check it with
> below:

Got it:

LSH-TEST:Found IRQ -1??

(rest is like everytime)

What to do now?

Nico

> [patch from Shaohua]
> +++ drivers/acpi/pci_irq.c   2004-12-07 15:05:38.709781248 +0800
> @@ -354,6 +354,13 @@ acpi_pci_irq_enable (
>          */
>         irq = acpi_pci_irq_lookup(dev->bus, PCI_SLOT(dev->devfn), pin,
> &edge_level, &active_high_low);
> 
> +       if (!irq) {
> +               printk("LSH-TEST:PCI interrupt %s[%c]: no GSI\n",
> +                       pci_name(dev), ('A' + pin));
> +               printk("LSH-TEST:BIOS assign IRQ %d\n", dev->irq);
> +       }else {
> +               printk("LSH-TEST:Found IRQ %d??\n", irq);
> +       }
>         /*
>          * If no PRT entry was found, we'll try to derive an IRQ from
> the

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  parent reply	other threads:[~2004-12-07 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200412070207.iB727OK6016916@fire-1.osdl.org>
2004-12-05 21:17 ` [nico-kernel-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org: [BUG] pdc202xx_new and ACPI fails] Nico Schottelius
     [not found]   ` <16A54BF5D6E14E4D916CE26C9AD30575B640E1-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
     [not found]   ` <20041205211754.GB7695-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
2004-12-05 22:36     ` Len Brown
2004-12-06 23:02       ` Nico Schottelius
2004-12-07  7:01       ` Nico Schottelius
2004-12-07 17:35       ` Nico Schottelius [this message]
2004-12-14 21:31       ` [fixed] pdc202xx_new and ACPI fails Nico Schottelius
2004-12-15  8:27       ` [BUG] " Nico Schottelius
     [not found]         ` <20041215082732.GA2273-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
2004-12-23 11:47           ` [BUG 3876] pdc202xx_new/ACPI: new data Nico Schottelius
     [not found] <16A54BF5D6E14E4D916CE26C9AD30575B640E1@pdsmsx402.ccr.corp.intel.com>

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=20041207173531.GA2289@schottelius.org \
    --to=nico-kernel-xuavfqxs+5hig4jrrz66wa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@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