From: Daniel Drake <dsd@gentoo.org>
To: Stian Jordet <liste@jordet.net>, sergio@sergiomb.no-ip.org
Cc: 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: Wed, 06 Sep 2006 19:49:36 -0400 [thread overview]
Message-ID: <44FF5E90.9030808@gentoo.org> (raw)
In-Reply-To: <1157557765.5091.1.camel@localhost.localdomain>
Stian Jordet wrote:
> On man, 2006-09-04 at 22:39 -0400, Daniel Drake wrote:
>> Stian Jordet wrote:
>>> Daniel Drake wrote:
>>>> Stian Jordet: You're on CC due to a discussion linked to from above where
>>>> it appeared that you needed Bjorn's patch. Please test this patch against
>>>> unmodified 2.6.17 or 2.6.18-rc and let us know if there are any problems.
>>>>
>>> No more usb for me with this patch :P
>> Please send dmesg from both a working kernel and a patched kernel, and
>> /proc/interrupts from both too.
>
> Here dmesg and /proc/interrupts with and without the patch. Both are
> 2.6.18-rc6...
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?
Daniel
next prev parent reply other threads:[~2006-09-06 23:49 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 [this message]
2006-09-07 2:00 ` Sergio Monteiro Basto
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=44FF5E90.9030808@gentoo.org \
--to=dsd@gentoo.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.helgaas@hp.com \
--cc=cw@f00f.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=sergio@sergiomb.no-ip.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