From owner-freebsd-current@FreeBSD.ORG Tue Oct 25 19:31:47 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFFCB16A41F for ; Tue, 25 Oct 2005 19:31:47 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 481B843D45 for ; Tue, 25 Oct 2005 19:31:47 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j9PJVi8M080977 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Oct 2005 23:31:45 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j9PJViZh080976; Tue, 25 Oct 2005 23:31:44 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 25 Oct 2005 23:31:44 +0400 From: Gleb Smirnoff To: Kris Kennaway Message-ID: <20051025193144.GU41520@cell.sick.ru> References: <025401c5d953$47004480$821cfa9e@mics.msu.su> <20051025174337.GA45694@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20051025174337.GA45694@xor.obsecurity.org> User-Agent: Mutt/1.5.6i Cc: Mike G , current@FreeBSD.org Subject: Re: uart and puc attach conflict X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2005 19:31:48 -0000 On Tue, Oct 25, 2005 at 01:43:37PM -0400, Kris Kennaway wrote: K> > I have a problem with multi-port card based on Nm9845 chip. K> > It's a card with 4 com-ports. K> > It perfectly works with puc(4) and sio(4) drivers if they compiled into K> > kernel. K> > or with puc(4) and uart(4) drivers if they loaded manualy. K> > But if puc(4) and uart(4) are compiled into kernel or loaded from K> > loader.conf - problem appears. K> K> Isn't puc superceded by uart? Why do you need both? Shouldn't uarts attach on puc? This is what I have in 5.4-STABLE system: puc0: mem 0xea202000-0xea202fff irq 5 at device 11.0 on pci0 uart0: <16750 or compatible> on puc0 uart1: <16750 or compatible> on puc0 uart2: <16750 or compatible> on puc0 uart3: <16750 or compatible> on puc0 uart4: <16750 or compatible> on puc0 uart5: <16750 or compatible> on puc0 uart6: <16750 or compatible> on puc0 uart7: <16750 or compatible> on puc0 Should it be other way in 6.0 and HEAD? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE