From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Stian Jordet <liste@jordet.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Daniel Drake <dsd@gentoo.org>,
akpm@osdl.org, torvalds@osdl.org, jeff@garzik.org,
greg@kroah.com, cw@f00f.org, bjorn.helgaas@hp.com,
linux-kernel@vger.kernel.org, harmon@ksu.edu,
len.brown@intel.com, vsu@altlinux.ru
Subject: Re: [PATCH V3] VIA IRQ quirk behaviour change
Date: Tue, 12 Sep 2006 13:37:20 +0100 [thread overview]
Message-ID: <1158064640.13591.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1158010698.23135.1.camel@localhost.localdomain>
On Mon, 2006-09-11 at 23:38 +0200, Stian Jordet wrote:
> On man, 2006-09-11 at 22:23 +0100, Sergio Monteiro Basto wrote:
> > On Mon, 2006-09-11 at 22:16 +0200, Stian Jordet wrote:
> > > On man, 2006-09-11 at 16:33 +0100, Sergio Monteiro Basto wrote:
> > > > On Sun, 2006-09-10 at 21:21 +0200, Stian Jordet wrote:
> > > > > On søn, 2006-09-10 at 20:41 +0100, Alan Cox wrote:
> > > > > > Feel free to cc me the lspci data and partial diagnostics and I'll try
> > > > > > and help too.
> > > > >
> > > > > Attached is lspci -xxx and dmesg from 2.6.18-rc6.
> > > > > http://bugzilla.kernel.org/show_bug.cgi?id=2874 has some further
> > > > > information about this (stupid) motherboard. Anything else you need?
> > > > >
> > > > > If anyone can help me with this, I'll promise to send the hero some
> > > > > boxes of Norwegian beer!
> > > > >
> > > > >
> > > > Hi, this isn't the case of one USB with IO-APIC-level on legacy
> > > > interrupts ?
> > > > 11: 5333 5326 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3
> > > >
> > > > if it is , was resolved with this [PATCH V3] VIA IRQ quirk behaviour change ?
> > >
> > > I have no idea what you mean here, but it's by no means fixed by that
> > > patch, actually it just got worse (usb didn't work, but still got
> > > interrupts from eth0 - and it still used irq 11)
> >
> > What ?! Aren't we talk about this computer
> > http://lkml.org/lkml/2006/9/6/178
> > and this
> > http://lkml.org/lkml/2006/9/7/220
> >
> > if you don't get your device quirked we have add your hardware to the
> > list ...
>
> That last patch there, made my system work (but that bugzilla bug is
> still a problem). So with that last patch, my system works just as good
> as it always has, if that's what you're trying to ask :)
Ok, as a quick answer, you have a very primitive VIA SMP board, which
make me remember my old laptop.
I maintain what a had write in previous emails about this system.
Seeing the configuration of irqs on windows, USB are in 9, so could be a
clue.
If I had your board, I'll try not quirk USB (cause quirk put USB in 11)
and make USB interrupts work as IO-APIC-edge.
9: nnnn nnnn IO-APIC-edge uhci_hcd:usb1, uhci_hcd:usb2,
uhci_hcd:usb3
--
Sérgio M. B.
next prev parent reply other threads:[~2006-09-12 12:36 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
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 [this message]
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=1158064640.13591.5.camel@localhost.localdomain \
--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