From owner-freebsd-current@FreeBSD.ORG Sun Nov 25 21:56:39 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 8BE2F16A41A for ; Sun, 25 Nov 2007 21:56:39 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.67]) by mx1.freebsd.org (Postfix) with ESMTP id 756C613C46E for ; Sun, 25 Nov 2007 21:56:39 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (asmtp001-s [10.150.69.64]) by smtpoutm.mac.com (Xserve/smtpout004/MantshX 4.0) with ESMTP id lAPLudsm020158; Sun, 25 Nov 2007 13:56:39 -0800 (PST) Received: from [192.168.1.100] (209-128-86-226.bayarea.net [209.128.86.226]) (authenticated bits=0) by mac.com (Xserve/asmtp001/MantshX 4.0) with ESMTP id lAPLuYV5021386 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 25 Nov 2007 13:56:35 -0800 (PST) Message-Id: <6CDF404E-3C97-485D-AC49-5674CFA5299D@mac.com> From: Marcel Moolenaar To: Frank Behrens In-Reply-To: <200711251246.lAPCkQiv088175@post.frank-behrens.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: Sun, 25 Nov 2007 13:56:33 -0800 References: <200711231457.lANEv4KU002862@post.frank-behrens.de> <200711251246.lAPCkQiv088175@post.frank-behrens.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: Sun, 25 Nov 2007 21:56:39 -0000 On Nov 25, 2007, at 4:46 AM, Frank Behrens wrote: > Marcel, > > thanks for your explanation. > > Marcel Moolenaar wrote on 24 Nov 2007 10:20: >> No, it isn't. The puc(4) driver can have different children. >> Currently, it >> can have 3 different children. Standard bus probing determines which >> driver will attach. The puc(4) driver does not care about unit >> numbers >> for >> the simple reason that it doesn't care about which driver attaches. > > OK. I interpret this as: It is not puc's problem, which sio units > are asssigned, it is the job for > the sio driver itself. 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. FYI, -- Marcel Moolenaar xcllnt@mac.com