From: Daniel Drake <dsd@gentoo.org>
To: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>, Chris Wedgwood <cw@f00f.org>,
greg@kroah.com, jeff@garzik.org, harmon@ksu.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add SATA device to VIA IRQ quirk fixup list
Date: Wed, 26 Jul 2006 15:31:02 +0100 [thread overview]
Message-ID: <44C77CA6.2050807@gentoo.org> (raw)
In-Reply-To: <1153922774.4486.7.camel@localhost.localdomain>
Sergio Monteiro Basto wrote:
> No, Quirks are only need when interrupts are in XT-PIC. (is my bet).
> When APIC and ACPI is enabled (and working) we don't need quirks.
>
> Someone said on XT-PIC VIA system, don't need, to boot, quirks when ACPI
> is disabled, but this statement don't prove that the quirk aren't need
> it .
No, please read again:
In the kernels referenced in the bug reports, the quirks were not being
applied.
When the systems booted up a usual APIC/ACPI config, the hardware in
question did not work. The quirk was not applied here.
When the system booted up a kernel with acpi=off, the hardware in
question worked fine. The quirk was not applied here.
When the kernel is modified to apply the quirk again, the system works
fine in both cases.
IOW, on these systems at least, the quirk is *definitely* needed when
ACPI/APIC are enabled, whereas in your last mail, you were suggesting we
should only do the quirk in non-APIC mode:
> I want put here something like: if ( dev->irq != XT-PIC) return and
> don't quirk this dev.
Such a change would stop the hardware in question from working when
ACPI/APIC are enabled on these systems.
Daniel
>> http://bugs.gentoo.org/138036
>> http://bugs.gentoo.org/141082
next prev parent reply other threads:[~2006-07-26 14:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 9:52 [PATCH] Add SATA device to VIA IRQ quirk fixup list Daniel Drake
2006-07-14 11:08 ` Jeff Garzik
2006-07-14 11:40 ` Daniel Drake
2006-07-14 11:51 ` Jeff Garzik
2006-07-14 12:15 ` Daniel Drake
2006-07-14 12:51 ` Sergey Vlasov
2006-07-14 13:20 ` Daniel Drake
2006-07-14 14:43 ` Andrew Morton
2006-07-14 15:42 ` Chris Wedgwood
2006-07-14 16:01 ` Scott J. Harmon
2006-07-14 16:17 ` Daniel Drake
2006-07-14 16:16 ` Chris Wedgwood
2006-07-14 16:24 ` Daniel Drake
2006-07-14 16:33 ` Chris Wedgwood
2006-07-14 16:51 ` Daniel Drake
2006-07-14 16:48 ` Sergio Monteiro Basto
2006-07-14 17:06 ` Daniel Drake
2006-07-14 17:21 ` Sergey Vlasov
2006-07-14 15:46 ` Sergio Monteiro Basto
2006-07-14 16:13 ` Chris Wedgwood
2006-07-15 0:10 ` Sergio Monteiro Basto
2006-07-16 14:09 ` Daniel Drake
2006-07-16 18:31 ` Greg KH
2006-07-17 0:34 ` Chris Wedgwood
2006-07-25 4:40 ` Andrew Morton
2006-07-26 0:42 ` Alan Cox
2006-07-26 12:45 ` Sergio Monteiro Basto
2006-07-26 13:59 ` Daniel Drake
2006-07-26 14:06 ` Sergio Monteiro Basto
2006-07-26 14:31 ` Daniel Drake [this message]
2006-07-26 15:11 ` Sergio Monteiro Basto
2006-07-26 22:14 ` Sergio Monteiro Basto
2006-07-14 23:58 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2006-07-14 19:26 Brown, Len
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=44C77CA6.2050807@gentoo.org \
--to=dsd@gentoo.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cw@f00f.org \
--cc=greg@kroah.com \
--cc=harmon@ksu.edu \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergio@sergiomb.no-ip.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