On Thu, 2006-06-22 at 16:25 -0700, Randy.Dunlap wrote: > No idea about that. > I think that you still didn't answer my question, or maybe I > didn't ask it well enough. What device are you having problems > with? I don't mean what chipset, I mean what device that you > touch... > I'd like to give you one answer , but I don't have one problem with one device, I bought (accidentally) one VIA with a Pentium dual-core, which have a bunch of problems. > > > --- orig/drivers/pci/quirks.c 2006-06-21 20:25:41.000000000 +1000 > > +++ linux-2.6.17-rc6-mm2/drivers/pci/quirks.c 2006-06-21 > 20:25:08.000000000 +1000 > > @@ -662,13 +662,7 @@ > > pci_write_config_byte(dev, PCI_INTERRUPT_LINE, > new_irq); > > } > > } > > -DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, > PCI_DEVICE_ID_VIA_82C586_0, quirk_via_irq); > > -DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, > PCI_DEVICE_ID_VIA_82C586_1, quirk_via_irq); > > -DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, > PCI_DEVICE_ID_VIA_82C586_2, quirk_via_irq); > > -DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, > PCI_DEVICE_ID_VIA_82C586_3, quirk_via_irq); > > -DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, > PCI_DEVICE_ID_VIA_82C686, quirk_via_irq); > > -DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, > PCI_DEVICE_ID_VIA_82C686_4, quirk_via_irq); > > -DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, > PCI_DEVICE_ID_VIA_82C686_5, quirk_via_irq); > > +DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, > quirk_via_irq); > > > > /* > > * VIA VT82C598 has its device ID settable and many BIOSes > > > > > > But do you know or not ? how I know if dev->irq is XT-pic ? > > I don't see a way to know that currently. It could be added > somehow if it's really required. So far I haven't seen a full > problem description or requirement for this. Well, this is based in tests along this 4 years, with my two computers. Like Bjorn said, we don't have any specification of VIA chipsets. But I like to try, use this quirks only if system don't have IO-APICs enabled. Many VIA systems work like that, for example my old laptop. For me, I know that my old laptop needs the quirks and run with interrupts in XT-PIC, and with my new desktop, I quit sure that don't need the quirks and system runs with interrupts in IO-APIC-edge and IO-APIC-level. Based in, what I read in this original thread http://lkml.org/lkml/2005/8/18/92 , seems to me, that we could try this solution, if we have a easy way to know what kind of interrupts have the device. Thanks Randy for your time, -- Sérgio M. B.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- References:
- Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
- From: Johny <[email protected]>
- Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
- From: Andrew Morton <[email protected]>
- Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
- From: Johny <[email protected]>
- 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]]
- From: Sergio Monteiro Basto <[email protected]>
- Re: 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]]
- From: "Randy.Dunlap" <[email protected]>
- 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]]
- From: Sergio Monteiro Basto <[email protected]>
- 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]]
- From: "Randy.Dunlap" <[email protected]>
- 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]]
- From: Sergio Monteiro Basto <[email protected]>
- 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]]
- From: "Randy.Dunlap" <[email protected]>
- 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]]
- From: Sergio Monteiro Basto <[email protected]>
- 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]]
- From: "Randy.Dunlap" <[email protected]>
- Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
- Prev by Date: 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]]
- Next by Date: Re: AGPGART: unable to get memory for graphics translation table.
- Previous by thread: 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]]
- Next by thread: 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]]
- Index(es):