From owner-freebsd-arch@FreeBSD.ORG Tue Nov 18 12:45:56 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C834C92C; Tue, 18 Nov 2014 12:45:56 +0000 (UTC) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7AF3DF7F; Tue, 18 Nov 2014 12:45:56 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1XqiAC-000P0U-Jl; Tue, 18 Nov 2014 16:45:44 +0400 Date: Tue, 18 Nov 2014 16:45:44 +0400 From: Slawa Olhovchenkov To: d@delphij.net Subject: Re: kernel linker: Overriding a driver shipped with kernel via module? Message-ID: <20141118124544.GA95731@zxy.spb.ru> References: <546A8191.3090208@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <546A8191.3090208@delphij.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: "weh@microsoft.com >> Wei Hu" , kyliel@microsoft.com, huishao@microsoft.com, "Jun Fang \(Wicresoft\)" , "freebsd-arch@FreeBSD.org Arch" , re X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2014 12:45:56 -0000 On Mon, Nov 17, 2014 at 03:15:29PM -0800, Xin Li wrote: > Right now one can declare version for a module by doing something like: > > MODULE_VERSION(module_name, module_version); > > Sometimes, it may be desirable for a vendor to release a new driver > that overrides the driver shipped with the kernel itself. However, it > seems that the MODULE_VERSION facility would just refuse the module > when preloaded with kernel. > > Looking at some other vendor drivers, they are using a slightly > different module name to overcome this limitation. Is that the only > way to do it? I think now time to move to modulated kernel and load all drivers currently present in GENERIC as modules (via loader.conf).