From owner-cvs-src@FreeBSD.ORG Fri Oct 8 22:41:27 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FCEA16A4CE; Fri, 8 Oct 2004 22:41:27 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1462743D2D; Fri, 8 Oct 2004 22:41:27 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i98MfJ1d029947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 8 Oct 2004 15:41:19 -0700 Message-ID: <4167178E.3050303@root.org> Date: Fri, 08 Oct 2004 15:41:18 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20041008212100.2BB2F5D04@ptavv.es.net> In-Reply-To: <20041008212100.2BB2F5D04@ptavv.es.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: John Baldwin Subject: Re: cvs commit: src/sys/dev/acpica acpi_quirks acpi_timer.c acpivar.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Oct 2004 22:41:27 -0000 Kevin Oberman wrote: >>Date: Fri, 08 Oct 2004 13:54:41 -0700 >>From: Nate Lawson >> >>John Baldwin wrote: >> >>>On Friday 08 October 2004 01:56 pm, Nate Lawson wrote: >>> >>> >>>>njl 2004-10-08 17:56:47 UTC >>>> >>>> FreeBSD src repository >>>> >>>> Modified files: >>>> sys/dev/acpica acpi_quirks acpi_timer.c acpivar.h >>>> Log: >>>> Update a quirk for the ASUS P5A to disable the timer. It appears to work >>>>fine with acpi but the timer runs twice as fast. Note that the main >>>>problem (system doesn't work properly with acpi disabled) should be fixed >>>>separately. >>> >>> >>>Actually, it's not really a problem that can be fixed. $PIR and the actual >>>link devices return different capabilities as far as the list of possible >>>IRQs for each link device. There's not much we can do to fix the fact that >>>according to ACPI, links 3 and 4 use IRQs 5 and 6 when $PIR says that neither >>>IRQ is valid for either link. >> >>I've been analyzing how Windows and Linux handle IRQ routing. There are >>some interesting parts that I've mentioned before but thought I'd >>summarize publically: >> >>* Some systems, notably laptops, require all PCI irqs to be routed to >>the SCI (irq 9 almost always). Sony VAIOs are one example. >> >>* Both $PIR and _PRT are used for ACPI irq routing. It merges them via >>some unknown algorithm (prefer $PIR?) >> >>As for this particular system, perhaps it would be helped by a PCI >>quirk. Also, was Kevin running the latest version of his BIOS? Also, >>the slot the ethernet card was in might change things. > > > Yes, it is the latest BIOS available. I doubt that ASUS will ever > release a new version, considering how old this card is. The BIOS I am > running was released on July 7, 1999. :-( > > I could move it to a different slot, I guess. Any reason for any > particular location? Some slots force irq sharing but if you have devices that can't handle that irq, they fail. This is especially on older systems that have an ISA and PCI slot that share an irq line. -- Nate