From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: kernel@agotnes.com, 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,
cw@f00f.org, vsu@altlinux.ru
Subject: Re: 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]]
Date: Thu, 22 Jun 2006 02:04:48 +0100 [thread overview]
Message-ID: <1150938288.3221.2.camel@localhost.portugal> (raw)
In-Reply-To: <20060621174754.159bb1d0.rdunlap@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 2591 bytes --]
who no, how sorry! I am a little tired
On Wed, 2006-06-21 at 17:47 -0700, Randy.Dunlap wrote:
> On Thu, 22 Jun 2006 01:36:46 +0100 Sergio Monteiro Basto wrote:
>
> > who I do know if a interrupt is ioapic_edge_type or ioapic_edge_type ?
>
> Do you mean how they are configured in a running kernel?
yes, I want to know in
linux-2.6.13/drivers/pci/quirks.c
when I am going quirk the PCI_VIA irq, if this irq is in
IO-APIC-something or is in XT-PIC , to decide if I quirk the interrupt
or not
>
> cat /proc/interrupts ::
>
> CPU0 CPU1
> 0: 12412944 12407808 IO-APIC-edge timer
> 1: 122673 124208 IO-APIC-edge i8042
> 7: 0 0 IO-APIC-edge parport0
> 9: 0 0 IO-APIC-level acpi
> 12: 1141950 1138138 IO-APIC-edge i8042
> 14: 1107749 1109102 IO-APIC-edge ide0
> 58: 451498 0 PCI-MSI eth0
> 66: 530689 495356 PCI-MSI libata
> 74: 0 0 IO-APIC-level ehci_hcd:usb1, uhci_hcd:usb6
> 82: 31 3 IO-APIC-level ohci_hcd:usb2, ohci_hcd:usb3, ohci_hcd:usb4, ohci_hcd:usb5
> 90: 561 492 IO-APIC-level HDA Intel
> 169: 3 0 IO-APIC-level ohci1394
> 177: 0 0 IO-APIC-level uhci_hcd:usb8
> 185: 0 0 IO-APIC-level uhci_hcd:usb7
> 193: 0 0 IO-APIC-level uhci_hcd:usb9
>
>
> or how they should be configured in case you are not sure?
> See a hardware spec. for that.
>
>
> > 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.
> >
>
>
> ---
> ~Randy
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: kernel@agotnes.com, 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,
cw@f00f.org, vsu@altlinux.ru
Subject: Re: 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]]
Date: Thu, 22 Jun 2006 02:04:48 +0100 [thread overview]
Message-ID: <1150938288.3221.2.camel@localhost.portugal> (raw)
In-Reply-To: <20060621174754.159bb1d0.rdunlap@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 2591 bytes --]
who no, how sorry! I am a little tired
On Wed, 2006-06-21 at 17:47 -0700, Randy.Dunlap wrote:
> On Thu, 22 Jun 2006 01:36:46 +0100 Sergio Monteiro Basto wrote:
>
> > who I do know if a interrupt is ioapic_edge_type or ioapic_edge_type ?
>
> Do you mean how they are configured in a running kernel?
yes, I want to know in
linux-2.6.13/drivers/pci/quirks.c
when I am going quirk the PCI_VIA irq, if this irq is in
IO-APIC-something or is in XT-PIC , to decide if I quirk the interrupt
or not
>
> cat /proc/interrupts ::
>
> CPU0 CPU1
> 0: 12412944 12407808 IO-APIC-edge timer
> 1: 122673 124208 IO-APIC-edge i8042
> 7: 0 0 IO-APIC-edge parport0
> 9: 0 0 IO-APIC-level acpi
> 12: 1141950 1138138 IO-APIC-edge i8042
> 14: 1107749 1109102 IO-APIC-edge ide0
> 58: 451498 0 PCI-MSI eth0
> 66: 530689 495356 PCI-MSI libata
> 74: 0 0 IO-APIC-level ehci_hcd:usb1, uhci_hcd:usb6
> 82: 31 3 IO-APIC-level ohci_hcd:usb2, ohci_hcd:usb3, ohci_hcd:usb4, ohci_hcd:usb5
> 90: 561 492 IO-APIC-level HDA Intel
> 169: 3 0 IO-APIC-level ohci1394
> 177: 0 0 IO-APIC-level uhci_hcd:usb8
> 185: 0 0 IO-APIC-level uhci_hcd:usb7
> 193: 0 0 IO-APIC-level uhci_hcd:usb9
>
>
> or how they should be configured in case you are not sure?
> See a hardware spec. for that.
>
>
> > 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.
> >
>
>
> ---
> ~Randy
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
next prev parent reply other threads:[~2006-06-22 1:05 UTC|newest]
Thread overview: 39+ 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:21 ` Johny
2006-06-20 11:40 ` Andrew Morton
2006-06-20 11:40 ` Andrew Morton
2006-06-20 13:22 ` Sergio Monteiro Basto
2006-06-20 13:22 ` Sergio Monteiro Basto
2006-06-21 10:50 ` Johny
2006-06-22 0:36 ` 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]] Sergio Monteiro Basto
2006-06-22 0:36 ` Sergio Monteiro Basto
2006-06-22 0:47 ` Randy.Dunlap
2006-06-22 0:47 ` Randy.Dunlap
2006-06-22 1:04 ` Sergio Monteiro Basto [this message]
2006-06-22 1:04 ` how I " Sergio Monteiro Basto
2006-06-22 4:08 ` Randy.Dunlap
2006-06-22 4:08 ` Randy.Dunlap
2006-06-22 11:56 ` Sergio Monteiro Basto
2006-06-22 11:56 ` Sergio Monteiro Basto
2006-06-22 21:29 ` Randy.Dunlap
2006-06-22 21:29 ` Randy.Dunlap
2006-06-22 22:46 ` Sergio Monteiro Basto
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-22 23:25 ` Randy.Dunlap
2006-06-23 1:30 ` Sergio Monteiro Basto
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:30 ` [linux-usb-devel] " Sergio Monteiro Basto
2006-06-20 13:59 ` Sergey Vlasov
2006-06-20 13:59 ` [linux-usb-devel] " 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=1150938288.3221.2.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=rdunlap@xenotime.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.