From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Johny <kernel@agotnes.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb-users@lists.sourceforge.net,
linux-usb-devel@lists.sourceforge.net, stern@rowland.harvard.edu,
Chris Wedgwood <cw@f00f.org>,
vsu@altlinux.ru
Subject: who I do know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
Date: Thu, 22 Jun 2006 01:36:46 +0100 [thread overview]
Message-ID: <1150936606.2855.21.camel@localhost.portugal> (raw)
In-Reply-To: <4499245C.8040207@agotnes.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
who I do know if a interrupt is ioapic_edge_type or ioapic_edge_type ?
On Wed, 2006-06-21 at 20:50 +1000, Johny wrote:
> Success :)
>
> I simply made the change
> manually, based on your and others' inputs (it seemed the simpler
> option).
>
> Both kernels now boot, and all USB devices are recognised correctly.
>
> I run in XT_PIC mode for interrupts.
>
Hi, thanks for your positive test on "my" theory.
Here it goes the link that I talked about on last email
http://lkml.org/lkml/2005/8/18/92 (you can read the previous messages on
this thread)
The patch of this link doesn't compile (at least for me), but have a
simple idea, which is just quirk the VIA_PCIs if they are in XT_PIC mode
and I think that is the way of this quirks should go.
So someone help me out and do a patch that recognize if the interrupt is
in XT-PIC mode or not ?
Thanks,
--
Sérgio M. B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
next prev parent reply other threads:[~2006-06-22 0:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 11:38 [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Johny Ågotnes
2006-06-20 11:21 ` Johny
2006-06-20 11:40 ` Andrew Morton
2006-06-20 13:22 ` Sergio Monteiro Basto
2006-06-21 10:50 ` Johny
2006-06-22 0:36 ` Sergio Monteiro Basto [this message]
2006-06-22 0:47 ` who I do know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]] Randy.Dunlap
2006-06-22 1:04 ` how I " Sergio Monteiro Basto
2006-06-22 4:08 ` Randy.Dunlap
2006-06-22 11:56 ` Sergio Monteiro Basto
2006-06-22 21:29 ` Randy.Dunlap
2006-06-22 22:46 ` Sergio Monteiro Basto
2006-06-22 22:54 ` Chris Wedgwood
2006-06-23 1:00 ` Sergio Monteiro Basto
2006-06-23 1:39 ` Randy.Dunlap
2006-06-23 1:50 ` Sergio Monteiro Basto
2006-06-23 2:02 ` Randy.Dunlap
2006-06-28 1:08 ` [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Sergio Monteiro Basto
2006-06-23 1:40 ` how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]] Johny
2006-06-22 23:25 ` Randy.Dunlap
2006-06-23 1:30 ` Sergio Monteiro Basto
2006-06-23 15:31 ` [linux-usb-devel] who I do " David Brownell
2006-06-20 12:09 ` [linux-usb-devel] [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Sergey Vlasov
2006-06-20 13:30 ` Sergio Monteiro Basto
2006-06-20 13:59 ` Sergey Vlasov
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=1150936606.2855.21.camel@localhost.portugal \
--to=sergio@sergiomb.no-ip.org \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=kernel@agotnes.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
--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