From owner-freebsd-arch Wed Feb 28 11: 1:24 2001 Delivered-To: freebsd-arch@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 494D937B718 for ; Wed, 28 Feb 2001 11:01:17 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA15272 for ; Wed, 28 Feb 2001 11:01:14 -0800 Date: Wed, 28 Feb 2001 11:01:07 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: arch@FreeBSD.ORG Subject: Re: lossage of a sort with using device hints... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's actually worse for me.... setting hint.isp.0.portwnn="0x50000000aaaa0000" hint.isp.0.nodewnn="0x50000000aaaa0001" guarantees me to be broken in that this will be forced to be type 'int' or type 'long'- and neither will correctly convert- and I can't even coerce this directly to a string- so I have to do something like: hint.isp.0.portwnn="w50000000aaaa0000" hint.isp.0.nodewnn="w50000000aaaa0001" in order to get the string so I can then do a kernel strtouq on the portion past the 'w'... *phppptttttt* > > I'm converting a driver over to using device hints instead of > getenv_*, and one thing has stubbed my toe. The current resource types are: > > > /* > * Resources from config(8). > */ > typedef enum { > RES_INT, RES_STRING, RES_LONG > } resource_type; > > > > But I've been happily using a getenv_quad for a 64 bit WWN override. > > It strikes me that RES_INT and RES_LONG are too vague (as well as useless). > How hard would it be to change these to RES_INT32 and RES_INT64? > > -matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message