From owner-freebsd-current@FreeBSD.ORG Mon Nov 26 18:00:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9970816A41A for ; Mon, 26 Nov 2007 18:00:18 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.75]) by mx1.freebsd.org (Postfix) with ESMTP id 834DD13C455 for ; Mon, 26 Nov 2007 18:00:18 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (asmtp009-s [10.150.69.72]) by smtpoutm.mac.com (Xserve/smtpout012/MantshX 4.0) with ESMTP id lAQI0IZH021652; Mon, 26 Nov 2007 10:00:18 -0800 (PST) Received: from mini-g4.jnpr.net (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mac.com (Xserve/asmtp009/MantshX 4.0) with ESMTP id lAQHxlwS013681 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 26 Nov 2007 09:59:54 -0800 (PST) Message-Id: <064AEB71-CE08-4850-BE1E-495A8997C003@mac.com> From: Marcel Moolenaar To: Frank Behrens In-Reply-To: <474AE5CC.9576.14C0917@frank.pinky.sax.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Mon, 26 Nov 2007 09:59:46 -0800 References: <200711231457.lANEv4KU002862@post.frank-behrens.de> <200711251246.lAPCkQiv088175@post.frank-behrens.de> <6CDF404E-3C97-485D-AC49-5674CFA5299D@mac.com> <474AE5CC.9576.14C0917@frank.pinky.sax.de> X-Mailer: Apple Mail (2.915) Cc: FreeBSD Current Subject: Re: Can not boot 7.0-BETA3 with puc 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: Mon, 26 Nov 2007 18:00:18 -0000 On Nov 26, 2007, at 6:27 AM, Frank Behrens wrote: > Marcel Moolenaar wrote on 25 Nov 2007 13:56: >> It's actually more a job for the newbus infrastructure. Whenever >> a child is created in a particular device class, it's assigned >> a unit number. Then and there do you want to implement policies >> about unit numbers. Not in the individual drivers, whether leave >> or otherwise. > > Do you believe I should create a PR, that we have a regression in > 7.0 for newbus > infrastructure? I don't think we have a regression in the newbus infrastructure, because we never had this support there. The problem has always been that we have treated the COM ports as a special case when we shouldn't have. Granted, other bugs forced us to treat the COM port specially (i.e. wiring the low-level console to a unit number before bus enumeration proper), but this is just more of the same... My suggestion is to use uart(4) and not worry about the unit number. Your console will work irrespective... -- Marcel Moolenaar xcllnt@mac.com