From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Daniel Drake <dsd@gentoo.org>, Linus Torvalds <torvalds@osdl.org>
Cc: Stian Jordet <liste@jordet.net>,
akpm@osdl.org, jeff@garzik.org, greg@kroah.com, cw@f00f.org,
bjorn.helgaas@hp.com, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, harmon@ksu.edu, len.brown@intel.com,
vsu@altlinux.ru
Subject: Re: [NEW PATCH] VIA IRQ quirk behaviour change
Date: Thu, 07 Sep 2006 03:00:42 +0100 [thread overview]
Message-ID: <1157594442.4700.9.camel@localhost.portugal> (raw)
In-Reply-To: <44FF5E90.9030808@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2222 bytes --]
On Wed, 2006-09-06 at 19:49 -0400, Daniel Drake wrote:
> Sergio,
>
> Stian appears to be walking proof that quirks are sometimes required
> in
> IO-APIC mode.
>
> My next move would be to modify the patch to not revert Bjorn's
> changes
> (but leave Linus' modification in place, alongside the southbridge
> detection). Any thoughts?
Hi Daniel, since you ask for thoughts :)
yap, is the obvious conclusion, but no, my bet is one problem with USB
and USB guys could put the USB things working.
I just had remember, my Asrock with VIA8237 and VIA SATA (where I am
write now) is working without quirks and USB guys made a patch, by
coincidence. Since then have been working great.
http://bugzilla.kernel.org/show_bug.cgi?id=6419#c19
About Linus patch I have to correct me about what I had write,
http://lkml.org/lkml/2005/9/27/113
«(it used to say "if we have an IO-APIC, don't do this" (my patch), now
it says "if this irq is bound to an IO-APIC, don't do this")»
Or my patch or the Linus patch, not both.
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -546,7 +546,10 @@ static void quirk_via_irq(struct pci_dev
{
u8 irq, new_irq;
- new_irq = dev->irq & 0xf;
+ new_irq = dev->irq;
+ if (!new_irq || new_irq >= 15)
+ return;
+
pci_read_config_byte(dev, PCI_INTERRUPT_LINE, &irq);
if (new_irq != irq) {
but I look to this Linus patch and I see 2 bugs
one should be > not >= and new_irq after tests new_irq should be dev->irq & 0xf;
like this:
- new_irq = dev->irq & 0xf;
+ new_irq = dev->irq;
+ if (!new_irq || new_irq > 15)
+ return;
+ new_irq = dev->irq & 0xf;
pci_read_config_byte(dev, PCI_INTERRUPT_LINE, &irq);
if (new_irq != irq) {
or simply :
+ if (!dev->irq || dev->irq > 15)
+ return;
new_irq = dev->irq & 0xf;
About Stian computer, looking for /proc/interrupts
11: 30696 27559 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3
have USB on irq 11, with IO-APIC-level, which less acpi is not normal on
low numbers ( <=15 ) be IO-APIC-level, normally is IO-APIC-edge.
Could be a ACPI problem .
Thanks,
--
Sérgio M. B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
next prev parent reply other threads:[~2006-09-07 2:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 2:04 [NEW PATCH] VIA IRQ quirk behaviour change Daniel Drake
2006-09-06 9:02 ` Stian Jordet
2006-09-05 2:39 ` Daniel Drake
2006-09-06 15:49 ` Stian Jordet
2006-09-06 23:49 ` Daniel Drake
2006-09-07 2:00 ` Sergio Monteiro Basto [this message]
2006-09-07 3:47 ` Daniel Drake
2006-09-07 11:43 ` Sergio Monteiro Basto
2006-09-07 21:07 ` Stian Jordet
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=1157594442.4700.9.camel@localhost.portugal \
--to=sergio@sergiomb.no-ip.org \
--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=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