Date: Sun, 25 Nov 2007 13:56:33 -0800 From: Marcel Moolenaar <xcllnt@mac.com> To: Frank Behrens <frank@pinky.sax.de> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Can not boot 7.0-BETA3 with puc Message-ID: <6CDF404E-3C97-485D-AC49-5674CFA5299D@mac.com> In-Reply-To: <200711251246.lAPCkQiv088175@post.frank-behrens.de> References: <200711231457.lANEv4KU002862@post.frank-behrens.de> <200711251246.lAPCkQiv088175@post.frank-behrens.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 25, 2007, at 4:46 AM, Frank Behrens wrote: > Marcel, > > thanks for your explanation. > > Marcel Moolenaar <xcllnt@mac.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6CDF404E-3C97-485D-AC49-5674CFA5299D>