From: Lee Revell <rlrevell@joe-job.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Greg KH <greg@kroah.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Daniel Drake <dsd@gentoo.org>,
akpm@osdl.org, torvalds@osdl.org, sergio@sergiomb.no-ip.org,
jeff@garzik.org, cw@f00f.org, bjorn.helgaas@hp.com,
linux-kernel@vger.kernel.org, harmon@ksu.edu,
len.brown@intel.com, vsu@altlinux.ru, liste@jordet.net
Subject: Re: [PATCH V3] VIA IRQ quirk behaviour change
Date: Tue, 19 Sep 2006 16:28:36 -0400 [thread overview]
Message-ID: <1158697716.13845.13.camel@mindpipe> (raw)
In-Reply-To: <20060919201231.GA7560@srcf.ucam.org>
On Tue, 2006-09-19 at 21:12 +0100, Matthew Garrett wrote:
> On Tue, Sep 19, 2006 at 04:04:27PM -0400, Lee Revell wrote:
> > On Sun, 2006-09-10 at 21:45 +0100, Matthew Garrett wrote:
> > > On Sun, Sep 10, 2006 at 02:40:46PM -0400, Lee Revell wrote:
> > >
> > > > Some applications such as realtime audio and probably gaming require
> > > > ACPI to be disabled, as it causes horrible latency problems. This
> > > > applies equally to Linux and Windows.
> > >
> > > How, and on what hardware?
> >
> > Here's a case where the kernel does not see a user's sound card at all
> > unless ACPI is disabled (second to last comment):
>
> That's more likely to be an interrupt routing issue than anything
> intrinsically awkward with ACPI.
>
True, but I was responding to an earlier statement along the lines of
"disabling ACPI is silly, who would do that?", and from these (and many
other) users' POV, they need to disable ACPI to have a working machine.
Lee
next prev parent reply other threads:[~2006-09-19 20:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 22:33 [PATCH V3] VIA IRQ quirk behaviour change Daniel Drake
2006-09-09 14:20 ` Alan Cox
2006-09-09 14:44 ` Daniel Drake
2006-09-09 16:03 ` Alan Cox
2006-09-09 21:34 ` Daniel Drake
2006-09-10 0:31 ` Alan Cox
2006-09-10 0:21 ` Greg KH
2006-09-10 0:39 ` Chris Wedgwood
2006-09-10 4:37 ` Greg KH
2006-09-10 9:48 ` Stian Jordet
2006-09-10 15:48 ` Daniel Drake
2006-09-10 18:40 ` Lee Revell
2006-09-10 20:45 ` Matthew Garrett
2006-09-10 21:30 ` Lee Revell
2006-09-10 21:34 ` Matthew Garrett
2006-09-19 20:04 ` Lee Revell
2006-09-19 20:12 ` Matthew Garrett
2006-09-19 20:28 ` Lee Revell [this message]
2006-09-10 16:01 ` Daniel Drake
2006-09-10 16:39 ` Alan Cox
2006-09-10 16:44 ` Jeff Garzik
2006-09-10 19:06 ` Daniel Drake
2006-09-10 19:41 ` Alan Cox
2006-09-10 19:21 ` Stian Jordet
2006-09-11 15:33 ` Sergio Monteiro Basto
2006-09-11 20:16 ` Stian Jordet
2006-09-11 21:23 ` Sergio Monteiro Basto
2006-09-11 21:38 ` Stian Jordet
2006-09-12 12:37 ` Sergio Monteiro Basto
2006-09-12 21:38 ` Stian Jordet
2006-09-13 0:48 ` Sergio Monteiro Basto
2006-09-11 21:54 ` Daniel Drake
2006-09-12 6:21 ` Stian Jordet
2006-09-11 21:44 ` Daniel Drake
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=1158697716.13845.13.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.helgaas@hp.com \
--cc=cw@f00f.org \
--cc=dsd@gentoo.org \
--cc=greg@kroah.com \
--cc=harmon@ksu.edu \
--cc=jeff@garzik.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liste@jordet.net \
--cc=mjg59@srcf.ucam.org \
--cc=sergio@sergiomb.no-ip.org \
--cc=torvalds@osdl.org \
--cc=vsu@altlinux.ru \
/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