From owner-freebsd-i386@FreeBSD.ORG Wed Aug 2 17:41:26 2006 Return-Path: X-Original-To: freebsd-i386@freebsd.org Delivered-To: freebsd-i386@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7838016A4DE; Wed, 2 Aug 2006 17:41:26 +0000 (UTC) (envelope-from jrhett@svcolo.com) Received: from outbound0.sv.meer.net (outbound0.mx.meer.net [209.157.153.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id D73AF43D70; Wed, 2 Aug 2006 17:41:24 +0000 (GMT) (envelope-from jrhett@svcolo.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id k72HfKjI056410; Wed, 2 Aug 2006 10:41:24 -0700 (PDT) (envelope-from jrhett@svcolo.com) Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id k72HepZP006133; Wed, 2 Aug 2006 10:40:51 -0700 (PDT) (envelope-from jrhett@svcolo.com) In-Reply-To: <20060803024810.X1573@epsplex.bde.org> References: <200607252036.k6PKanFd072593@www.freebsd.org> <20060731191302.S1172@epsplex.bde.org> <6EFF87DF-280C-402C-8C2A-10F3144CF41F@svcolo.com> <20060802205230.N90692@delplex.bde.org> <20060802234330.J1249@epsplex.bde.org> <20060802150656.GB47835@svcolo.com> <20060803024810.X1573@epsplex.bde.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <83D35AA9-61D2-4977-AFEC-C498F4147FC2@svcolo.com> Content-Transfer-Encoding: 7bit From: Jo Rhett Date: Wed, 2 Aug 2006 10:40:49 -0700 To: Bruce Evans X-Mailer: Apple Mail (2.752.2) Cc: njl@freebsd.org, freebsd-gnats-submit@freebsd.org, freebsd-i386@freebsd.org Subject: Re: i386/100831: sio ignores BIOS information about serial ports - bounty offered X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Aug 2006 17:41:26 -0000 > On Wed, 2 Aug 2006, Jo Rhett wrote: >> 1. We can't/won't fix the sio0<->sio1 problem because fixing ACPI >> is hard On Aug 2, 2006, at 10:25 AM, Bruce Evans wrote: > _I_ can't/won't fix it because not just the above :-). Swapping of > consoles > only could be fixed within the driver (so that ACPI is not involved > and > you don't have to change device.hints) since consoles have to be > hard-wired > in some way and the hints are good enough for wiring the unit > number to > the i/o address (provided it's an old ISA port -- otherwise hints > based > on the i/o address don't work). Sorry, color me dumb. I'm getting lost here. The problem I was observing is that device hints is being (mostly) ignored by ACPI and thus this is the root problem to fix. I'm not sure what you're trying to say here. >> 2. The sio units are thus going to swap when entering high-level >> sio mode >> 3. The workaround is to put flags 0x10 (or 0x90) on sio1 > > It also needs the port numbers swapped (for consoles to work) and > other hints > swapped (to be consistent, so as to work if there is no ACPI so the > other > hints are actually used) Can you provide a clear list of instructions then? I have no idea what you mean by "port numbers swapped". Swapped where? I was assuming /boot.config has -Dh /boot/loader.conf has console="comconsole" /boot/device.hints comment out #hint.sio.0.flags="0x10" /boot/device.hints add hint.sio.1.flags="0x10" /etc/ttys - put a getty on ttyd1 What am I missing? If I understand correctly, the boot loader compiled in option sio0 on 0x3f8 flags 0x10 will be in effect until the higher level sio driver is loaded, at which point it reassigns all the ports based on ACPI and device.hints and the two changes to device.hints above will take effect, yes? >> 4. There should be no ill effect from doing this. Console will >> never break >> and go to the wrong port. > > Yes, "should be". The wiring should be fairly deterministic once you > get it to work. I think it will continue to work even if someone > fixes > (?) ACPI to prefer the hints order to the ACPI order. However, it > would > break if someone fixes (?) ACPI to prefer the BIOS order to both > the hints > order and the ACPI order (I think ACPI is using its own order and > doesn't > know that you've swapped the order in the BIOS). I'm not sure I understand the difference. The ACPI order is the order that the BIOS presents them in when querying it via ACPI, yes? -- Jo Rhett senior geek Silicon Valley Colocation