From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 17:34:42 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4E6916A41F for ; Mon, 31 Oct 2005 17:34:42 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4258543D49 for ; Mon, 31 Oct 2005 17:34:42 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9VHY8uO005589; Mon, 31 Oct 2005 10:34:08 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 31 Oct 2005 10:34:08 -0700 (MST) Message-Id: <20051031.103408.71093019.imp@bsdimp.com> To: marcolz@stack.nl From: Warner Losh In-Reply-To: <20051031160150.GB87483@stack.nl> References: <20051031151809.GA83253@stack.nl> <43663A0A.4040608@samsco.org> <20051031160150.GB87483@stack.nl> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 31 Oct 2005 10:34:11 -0700 (MST) Cc: stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 17:34:42 -0000 > > The ACPI+sio problem is known. I have a motherboard with a similar > > problem, though a different brand than yours. I solved it by removing > > the ACPI attachment from the sio code. The better solution is to allow > > loader hints to override ACPI hints. I tried talking to John Baldwin > > about this but didn't get much of a response. > > I've tried all suggestions so far, but to no avail on most servers. Too > many broken ACPI implementations I fear... Too bad motherboard vendors > don't take the time to push proper software in their flash. Right now acpi tells us there's a device, and we use it. Loader hints should be used to map locations to device instances. It is more general than just ACPI, however. People want to bind sio to a specific port that comes out the back. People also want to bind rl0 to the card in slot 3. Consider my system: sio0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.SBRG.UAR1 sio1 pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.SBRG.UAR2 On this system, UAR1 is the port that comes out the back, so I have what I want. However, I'd like to be able to say: hint.sio.0.at="acpi" hint.sio.0.location="\_SB_.PCI0.SBRG.UAR2" or hint.sio.0.at="acpi" hint.sio.0.location="UAR2" or hint.fxp.0.at="pci" hint.fxp.0.location="bus=2 slot=3 function=0" hint.fxp.1.at="pci" hint.fxp.1.location="pci2:2:0" Since we really want to map the devices in some arbitrary ACPI tree to instances in the system, rather than mapping devices that happen to live at a specific resource address to specific instances in the tree. However, there are a number of issues in doing this generically and with error cases. How does one deal with the different syntaxes? What extensions to the newbus system are there? etc. Warner