From owner-freebsd-embedded@FreeBSD.ORG Wed Jan 2 18:05:07 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 910FB16A419 for ; Wed, 2 Jan 2008 18:05:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 3B00313C465 for ; Wed, 2 Jan 2008 18:05:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8q) with ESMTP id 227032756-1834499 for multiple; Wed, 02 Jan 2008 13:03:00 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id m02I4kCj018326; Wed, 2 Jan 2008 13:04:52 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marcel Moolenaar Date: Wed, 2 Jan 2008 12:30:01 -0500 User-Agent: KMail/1.9.6 References: <200712311606.25424.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801021230.01517.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 02 Jan 2008 13:04:52 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/5343/Wed Jan 2 12:41:01 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-embedded@freebsd.org Subject: Re: ocpbus(4) X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2008 18:05:07 -0000 On Tuesday 01 January 2008 03:09:50 pm Marcel Moolenaar wrote: > > On Dec 31, 2007, at 1:06 PM, John Baldwin wrote: > > >> Using the hints-way of describing hardware is just not going to > >> fly in that case, because you're still keying off of device names > >> and unit numbers. Let that be a consequence of the metadata, not > >> an integral part of... (device.COM1.* does exactly that). > > > > Redo the 'at' hints like this (pci was already this way in the > > existing hint > > wiring stuff anyway, i.e. it's _not_ a new-bus device name in > > 'at'). I'll > > use all-caps to make it stand out: > > While I think that's a good thing, the confusion to the user > when it comes to the unit number is already present. People > already assume that if they have hint.sio.0.at="isa" that > they expect to see device sio0. I fear that it's exactly the > same with "device.COM1.at=ISA. If the 1 on COM1 is just a > means to distinguish multiple COM devices, then it's much > better to use a more structural approach, eliminate the unit > and instead key-off of something that's truly identifying. It's a string. Look at your PC, on the back it has a label with "COM1" or "COMA" or some such. You can call it 'device.IHATECOMPUTERS' if you want. The idea is to just give a collection of properties a name so that they can all be bound together. > In other words: hints historically mix the hardware description > with the assignment of the driver and the unit number. Your > proposal has the same flaws. The whole thing is just awkward > for the user and impossible to implement unambiguously. COM1 is not a new-bus name. Nowhere in any of the device.FOO is a single new-bus name execept for the possible 'driver=foo' property to bind to a driver. That all said, I obviously am unable to come up with anything acceptable to your tastes so I'll just give up and work on something else. -- John Baldwin