linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew de Quincey <adq_dvb@lidskialf.net>
To: Alexander Rau <al.rau@gmx.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI patch which fixes all my IRQ problems on nforce2 -- linux-2.5.75-acpi-irqparams-final4.patch
Date: Mon, 28 Jul 2003 16:38:24 +0100	[thread overview]
Message-ID: <200307281638.24474.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <3F25419B.2050607@gmx.de>

On Monday 28 July 2003 16:30, Alexander Rau wrote:
> Andrew de Quincey wrote:
> > This is version final4 of the patch now. Improvement over version final3
> > is a fix to IRQ allocation.. previously all PCI IRQs were allocated to
> > IRQ11 on my Thinkpad.
> >
> > This _may_ break ACPI IRQ routing on the Toshiba 5005-S504  (I hope I
> > have managed to support it though). Can someone check please? Quote from
> > pci_link.c:
> >          * Note that we don't validate that the current IRQ (_CRS) exists
> >          * within the possible IRQs (_PRS): we blindly assume that
> > whatever * IRQ a boot-enabled Link device is set to is the correct one. *
> > (Required to support systems such as the Toshiba 5005-S504.)
>
> I tried to apply the patch to 2.6.0-test2 in hope that this resolves my
> oops during boottime on my thinkpad t40p.
>
> Unfortunatly the compilation of the kernel fails with:
>
> ---------------------------------------------------------------------------
>-- CC      drivers/acpi/pci_link.o
> drivers/acpi/pci_link.c: In function `acpi_pci_link_allocate':
> drivers/acpi/pci_link.c:451: `_dbg' undeclared (first use in this function)
> drivers/acpi/pci_link.c:451: (Each undeclared identifier is reported
> only once
> drivers/acpi/pci_link.c:451: for each function it appears in.)
> make[2]: *** [drivers/acpi/pci_link.o] Error 1
> make[1]: *** [drivers/acpi] Error 2
> make: *** [drivers] Error 2
> ---------------------------------------------------------------------------
>--
>
> Any ideas how to port your patch to the 2.6 series ?

Weird! I compiled it on 2.6.0-test2 last night (for a thinkpad T20), and it 
was fine..... (and the thinkpad works fine too)

Send me your .config file so I can fix the patch, please.



  reply	other threads:[~2003-07-28 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-27 22:05 [PATCH] ACPI patch which fixes all my IRQ problems on nforce2 -- linux-2.5.75-acpi-irqparams-final4.patch Andrew de Quincey
2003-07-28 15:30 ` Alexander Rau
2003-07-28 15:38   ` Andrew de Quincey [this message]
     [not found]     ` <3F2546EF.9030803@gmx.de>
     [not found]       ` <200307281653.58216.adq_dvb@lidskialf.net>
2003-07-28 16:25         ` Alexander Rau
2003-07-28 20:57           ` Alexander Rau
2003-07-28 21:16             ` Andrew de Quincey
2003-07-29  8:46               ` Thomas Schlichter
2003-07-28 19:51     ` Andrew Morton
2003-07-28 20:26       ` Andrew de Quincey
2003-07-28 15:42   ` Compile error with 2.6.0-test2 config attached lkml
2003-07-28 15:53   ` [PATCH] ACPI patch which fixes all my IRQ problems on nforce2 -- linux-2.6.0-test2-acpi-irqparams-final5.patch Andrew de Quincey

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=200307281638.24474.adq_dvb@lidskialf.net \
    --to=adq_dvb@lidskialf.net \
    --cc=al.rau@gmx.de \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).