From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58494) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YsRoO-00070I-7c for qemu-devel@nongnu.org; Wed, 13 May 2015 04:14:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YsRoK-0007C0-Qz for qemu-devel@nongnu.org; Wed, 13 May 2015 04:14:40 -0400 Received: from isrv.corpit.ru ([86.62.121.231]:52328) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YsRoK-000785-IZ for qemu-devel@nongnu.org; Wed, 13 May 2015 04:14:36 -0400 Message-ID: <555307E4.8050102@msgid.tls.msk.ru> Date: Wed, 13 May 2015 11:14:28 +0300 From: Michael Tokarev MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] modules: enabling other kinds of modules, not only block? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Hello. Is there any interest of enabling other kinds of modules, not only block? Eg, modular display (gtk/sdl/..) would be nice (but not exactly easy with sdl1), smartcard-nss device can be built as module and so on. Also, how about on-demand module loading? I see quite easy way of doing so, first lookup in the currently registered device/block-type list, and if not found, see if we have it in one of known modules, try to load it if found. I once did the 2nd thing but now things has changed in this area so I'll have to redo it. Thanks, /mjt