From owner-freebsd-stable@FreeBSD.ORG Mon Sep 15 16:48:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A2B9F106566C for ; Mon, 15 Sep 2008 16:48:41 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id 8487C8FC2D for ; Mon, 15 Sep 2008 16:48:40 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id m8FGmcfi085459; Tue, 16 Sep 2008 02:48:38 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 16 Sep 2008 02:48:38 +1000 (EST) From: Ian Smith To: Andriy Gapon In-Reply-To: <48CE815A.9040907@icyb.net.ua> Message-ID: <20080916021035.N439@sola.nimnet.asn.au> References: <48CE5E9B.9000304@icyb.net.ua> <20080916002823.E439@sola.nimnet.asn.au> <48CE815A.9040907@icyb.net.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: FreeBSD Stable Subject: Re: sio => uart: one port is gone 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, 15 Sep 2008 16:48:41 -0000 On Mon, 15 Sep 2008, Andriy Gapon wrote: > on 15/09/2008 17:36 Ian Smith said the following: > > On Mon, 15 Sep 2008, Andriy Gapon wrote: > > > This is a fairly standard and old machine with 2 COM ports. > > > Recently (last Friday) I decided to update my RELENG_7 system and also > > > to transition from sio to uart. > > > > This what I had before the upgrade: > > > kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags > > > 0x10 on acpi0 > > > kernel: sio0: type 16550A > > > kernel: sio0: [FILTER] > > > kernel: sio1: <16550A-compatible COM port> port 0x2e8-0x2ef irq 3 on acpi0 > > > kernel: sio1: type 16550A > > > kernel: sio1: [FILTER] > > > > This is what I have now: > > > uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > > > uart0: [FILTER] > > > > This is what I have in device.hints for uart: > > > hint.uart.0.at="isa" > > > hint.uart.0.port="0x3F8" > > > hint.uart.0.flags="0x10" > > > hint.uart.0.irq="4" > > > hint.uart.1.at="isa" > > > hint.uart.1.port="0x2F8" > > > > but it's shown as 0x2e8 above .. > > > > > hint.uart.1.irq="3" > > > hint.uart.2.at="isa" > > > > Precisely the same hints (s/uart/sio/) I had for sio. > > > > 0x2f8 is 'standard COM2' address .. did sio1 work ok at 0x2e8 before? > thank you, I guess I had a typo in my hints, but the port did work. > Looking at the old dmesg I see that sio devices are found 'on acpi0' as > opposed to uart now being found on 'isa0'. > Maybe this is another difference. Does sound a bit odd; looks like the ACPI info trumped hints for sio. > Maybe sio was attached using some information from acpi, so hints were not > that important. But maybe the same acpi information is not applied to uart, > so it does depend on the hints. Sounds a reasonable theory .. so does fixing that hint find the UART? Maybe a verbose dmesg would provide more clues re uart's attachment? > If this guess is correct then this is a regression in sio=>uart transition, > if not, then I'll just correct my device.hints and shut up :-) Or both :) You'd think if ACPI info is available uart should use it, but then if it's attaching to the isa bus instead, maybe not .. hmm. cheers, Ian