From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 21 22:21:53 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D65F616A41A for ; Tue, 21 Aug 2007 22:21:53 +0000 (UTC) (envelope-from cnst@FreeBSD.org) Received: from mojo.ru (mojo.ru [84.252.152.63]) by mx1.freebsd.org (Postfix) with ESMTP id 4955513C442 for ; Tue, 21 Aug 2007 22:21:53 +0000 (UTC) (envelope-from cnst@FreeBSD.org) Received: from [192.168.0.16] (nc-76-4-28-21.dhcp.embarqhsd.net [76.4.28.21]) (authenticated bits=0) by mojo.ru (8.12.11.20060308/8.12.10) with ESMTP id l7LM8iiC021991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Aug 2007 02:08:47 +0400 Message-ID: <46CB625D.7040505@FreeBSD.org> Date: Tue, 21 Aug 2007 18:08:29 -0400 From: "Constantine A. Murenin" Organization: Google Summer of Code 2007 Student @ The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-gb, en-gb-oed, en, en-us, ru, ru-ru, ru-su MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: "Constantine A. Murenin" Subject: device hints for isa modules X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 22:21:53 -0000 Dear freebsd-hackers@, Is there a way to statically compile device hints into an isa(4) module? From what it looks, there is no place in the source tree to put the hints for isa(4) modules -- you either have to place default hints into GENERIC.hints, implying that the driver will be compiled into a GENERIC kernel, or place it into NOTES. In the former case, having a module is then useless; in the latter, the module simply ain't going to work. This is complicated further by the fact that changing isa hints after the boot has no effect on isa driver modules that use standard methods of resource acquisition. (Specifically, notice that kenv(1) won't give you an error message when you try to create a new hint or update an existing one, and the new or updated hint will in fact be visible back from kenv(1), but it won't have any effect on bus_alloc_resource(9) calls, thus modules depending on isa hints will fail to find their hardware.) I'm specifically looking for a solution to a usable module for my lm(4) driver in soc2007/cnst-sensors perforce branch... Cheers, Constantine.