From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Bive1-0006sf-HA for qemu-devel@nongnu.org; Fri, 09 Jul 2004 09:42:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Bive0-0006sT-2b for qemu-devel@nongnu.org; Fri, 09 Jul 2004 09:42:29 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bivdz-0006sQ-VY for qemu-devel@nongnu.org; Fri, 09 Jul 2004 09:42:28 -0400 Received: from [213.146.130.142] (helo=trantor.org.uk) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1BivbN-0007j1-Lz for qemu-devel@nongnu.org; Fri, 09 Jul 2004 09:39:45 -0400 Subject: Re: [Qemu-devel] plugins From: Gianni Tedesco In-Reply-To: <40EFD7E2.7000607@witch.dyndns.org> References: <40ED8EF0.1040501@bellard.org> <40EF1357.1000600@witch.dyndns.org> <40EFD7E2.7000607@witch.dyndns.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-uQQ5Zp1dzMNsC99MPU9d" Date: Fri, 09 Jul 2004 14:39:46 +0100 Message-Id: <1089380386.3101.11.camel@sherbert> Mime-Version: 1.0 Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --=-uQQ5Zp1dzMNsC99MPU9d Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2004-07-10 at 14:49 +0300, Hetz Ben Hamo wrote: > With a plugin system (all it takes is 2 files: an text/XML file which=20 > contains the info on this plugin, and a .so file which is the plugin=20 > itself) both closed source and open source developers can add lots of=20 > hardware to QEMU which can be used for driver development on Linux and=20 > on Windows (as well other guest OS's) without having the real hardware. 2 files? whatever goes in the text/xml file can go inside the DSO just as easily... > Have you ever thought to write driver for Linux for some hardware (which=20 > someone can writes a plugin) without having it? now you (potentially) can= .. All I'd like to see changed in the device API is the ability to have a bit more control over where devices go and make all devices clean to be used multiple times (ie. like you can have as many NICs as you like). Then I'd like to see hw/pc.c and hw/ppc.c etc.. go away to be replaced with 'hardware description files'... I think that if you wanted to allow the same code to be used by each of the different CPU emulations, that would be more difficult and could slow things down at runtime. --=20 // Gianni Tedesco (gianni at scaramanga dot co dot uk) lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import 8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D --=-uQQ5Zp1dzMNsC99MPU9d Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBA7qAhkbV2aYZGvn0RAvjDAJ0fMJxhHyl2L25jd0LVCgwO6DZ8RgCeNsGd vaeuChYF3+rguWgVG/uxMNo= =YYmp -----END PGP SIGNATURE----- --=-uQQ5Zp1dzMNsC99MPU9d--