From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: [PATCH] VIA IRQ quirk for 2.6.12-rc5 Date: Fri, 27 May 2005 11:09:17 +0100 Message-ID: <1117188546.5730.175.camel@localhost.localdomain> References: <20050527082150.GA24428@toshiba.hsd1.ma.comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20050527082150.GA24428-g3qfMnKXm6l/wjb6y0L7XlrsPObopucw0e7PPNI6Mm0@public.gmane.org> Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Len Brown Cc: torvalds-3NddpPZAyC0@public.gmane.org, Linux Kernel Mailing List , acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, bjorn.helgaas-VXdhtT5mjnY@public.gmane.org List-Id: linux-acpi@vger.kernel.org On Gwe, 2005-05-27 at 09:21, Len Brown wrote: > Delete quirk_via_bridge(), restore quirk_via_irqpic() -- > but now improved to be invoked upon device ENABLE, and > now only for VIA devices -- not all devices behind VIA bridges. Properly you should apply the fixup to all VBUS devices. I've not seen a clean way to identify which devices fall into that category but there are public data sheets for many of the chips. > + printk(KERN_INFO "PCI: Via PIC IRQ fixup for %s, from %d to %d\n", > + pci_name(dev), irq, new_irq); > + udelay(15); /* unknown if delay really needed */ > + pci_write_config_byte(dev, PCI_INTERRUPT_LINE, new_irq); It isn't ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005