public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: akpm@osdl.org, ktech@wanadoo.es,
	david+challenge-response@blue-labs.org,
	acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	a.verweij@student.tudelft.nl
Subject: Re: [ACPI] acpi problem with nforce motherboards and ethernet
Date: Sat, 7 Feb 2004 03:50:18 +0100	[thread overview]
Message-ID: <20040207035018.33ce01dc.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.55.0402070021210.12260@jurand.ds.pg.gda.pl>

On Sat, 7 Feb 2004 00:33:04 +0100 (CET)
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl> wrote:


>  That's not the right fix.  There's a bug in Linux's ACPI IRQ setup as
> I've discovered by comparing the code to the spec.  Here's a patch I sent
> in December both to the LKML and the ACPI maintainer.  The feedback from
> the list was positive, but the maintainer didn't bother to comment.

Thanks. I added the patch to the x86-64 sources and it indeed seems to fix
the Nforce3.

-Andi

  reply	other threads:[~2004-02-07  2:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 19:25 acpi problem with nforce motherboards and ethernet Luis Miguel García
     [not found] ` <402298C7.5050405-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org>
2004-02-05 19:44   ` David Ford
     [not found]     ` <40229D2C.20701-qokYbnrgTHEgsBAKwltoeQ@public.gmane.org>
2004-02-05 21:27       ` Luis Miguel García
     [not found]         ` <4022B55B.1090309-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org>
2004-02-05 23:40           ` Andrew Morton
     [not found]             ` <20040205154059.6649dd74.akpm-3NddpPZAyC0@public.gmane.org>
2004-02-06  0:08               ` Prakash K. Cheemplavam
2004-02-06  0:14               ` Craig Bradney
     [not found]                 ` <1076026496.16107.23.camel-V9bJ71E8C7qMuHbpHUh99CT4j+jCus6s@public.gmane.org>
2004-02-06  0:22                   ` Luis Miguel García
     [not found]                     ` <4022DE3C.1080905-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org>
2004-02-06  0:38                       ` Prakash K. Cheemplavam
2004-02-06  0:46                         ` [ACPI] " Luis Miguel García
     [not found]                           ` <4022E3C8.4020704-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org>
2004-02-06  0:59                             ` Craig Bradney
2004-02-06  0:56                       ` Craig Bradney
2004-02-06 23:33               ` Maciej W. Rozycki
2004-02-07  2:50                 ` Andi Kleen [this message]
     [not found]                 ` <Pine.LNX.4.55.0402070021210.12260-rsPqkUlH4Vdx0R2ya2r/wqsMm+1xrEX8@public.gmane.org>
2004-02-07  6:29                   ` Luis Miguel García
2004-02-06  9:47           ` Daniel Drake
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 17:41 Luis Miguel García
2004-02-05 18:41 ` [ACPI] " Arjen Verweij

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=20040207035018.33ce01dc.ak@suse.de \
    --to=ak@suse.de \
    --cc=a.verweij@student.tudelft.nl \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=david+challenge-response@blue-labs.org \
    --cc=ktech@wanadoo.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    /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