From owner-freebsd-acpi@FreeBSD.ORG Thu Jul 6 20:15:53 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B828D16A4DA for ; Thu, 6 Jul 2006 20:15:53 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 250AE43D46 for ; Thu, 6 Jul 2006 20:15:52 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout6-ext.prodigy.net (pimout6-int.prodigy.net [207.115.4.22]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k66KG7Eq010949 for ; Thu, 6 Jul 2006 16:16:07 -0400 X-ORBL: [67.119.74.222] Received: from [10.0.0.53] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by pimout6-ext.prodigy.net (8.13.6 out.dk/8.13.6) with ESMTP id k66KFj5S242404; Thu, 6 Jul 2006 16:15:46 -0400 Message-ID: <44AD6F67.9060804@root.org> Date: Thu, 06 Jul 2006 13:15:35 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: othermark References: <200607050838.44324.jhb@freebsd.org> <200607060700.22376.jhb@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: acpi on msi-9218 (-current) swaps sio0 and sio1 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 20:15:53 -0000 othermark wrote: > John Baldwin wrote: > >> On Wednesday 05 July 2006 14:14, othermark wrote: >>> John Baldwin wrote: >>> >>>> On Thursday 29 June 2006 17:51, othermark wrote: >>>>> With acpi loaded on a msi-9218 motherboard, I'm seeing sio0 and sio1 >>>>> get 'swapped.' Even though the kernel is compiled for console on >>>>> 0x3f8, I've had to change the /etc/ttys to use ttyd1 so login is >>>>> displayed when the system is booted. >>>>> >>>>> Empirically, this tells me that 0x3f8 is correct for sio0 (since the >>>>> kernel and boot loader display fine using it as comconsole). >>>>> >>>>> Is there a way to force this to be consistant? This is -current from >>>>> Jun >>>>> 8. I will try a more recent kernel soon. The following is a verbose >>>>> boot log. >>>> This is because your BIOS lists them backwards in the ASL. There isn't >>>> a workaround currently short of fixing your ASL to list them in the >>>> COM1/COM2 order and building a custom dsdt. >>> Many thanks for your input, >>> >>> So would it be sufficient in the _INI method, just to swap the >>> order of initialization (I'm guessing here) for the COMA and COMB >>> sections? COMA and COMB both have full resource templates for all >>> possible legal settings. >> No, you have to swap the COMA and COMB devices themselves. > > Ahh ok. You must forgive me if I seem dense since this is the first time > I've looked at repairing these types of instruction files. Are you saying > that the order that they appear in the .asl is important? Yes, that's what he means. Move the whole Device (COMA) { ... } section before COMB if that's what you want. Ultimate solution is probably to implement _SRS support (set resource) so that we can reconfigure the devices according to their desired order. That's not even on anyone's todo list I think. -- Nate