qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hetz Ben Hamo <hetz@witch.dyndns.org>
To: qemu-devel@nongnu.org, Johannes.Schindelin@gmx.de
Subject: [Qemu-devel] plugins
Date: Sat, 10 Jul 2004 14:49:54 +0300	[thread overview]
Message-ID: <40EFD7E2.7000607@witch.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0407091148580.8873@wgmdd8.biozentrum.uni-wuerzburg.de>

> There is already a plugin system. It requires you to recompile everytime
> you add a new piece of hardware, though. I don't think this is a problem
> as most likely you will have to recompile anyway to make sure the plugin
> uses the same header files as qemu's core.

Yes, but this plugin method is not very usefull for 3rd party plugins..

Many people don't realize one thing about QEMU which differs it from ANY 
other emulator: For the first time, you can create a "hardware card", 
write drivers for it and test it on guest OS's (Windows, Linux, *BSD, 
etc) and test it on other platforms (PPC, Sparc, ARM, once their core is 
matured).

Think about it: You can create a new PCI card without buying those all 
expensive software to simulate it, write drivers to test it and if it 
works well for your customer(s), you can do the real PCI card! Go try 
that with VMWare (you can't), BOCHS (good luck hacking their code, and 
see the speed difference), and I'm not even mentioning PPC, ARM or Sparc...

With a plugin system (all it takes is 2 files: an text/XML file which 
contains the info on this plugin, and a .so file which is the plugin 
itself) both closed source and open source developers can add lots of 
hardware to QEMU which can be used for driver development on Linux and 
on Windows (as well other guest OS's) without having the real hardware.

Have you ever thought to write driver for Linux for some hardware (which 
someone can writes a plugin) without having it? now you (potentially) can..

Just my thoughts...
Thanks,
Hetz

  reply	other threads:[~2004-07-09 11:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08 18:14 [Qemu-devel] RFC for new features Fabrice Bellard
2004-07-08 18:46 ` [Qemu-devel] " Emmanuel Charpentier
2004-07-08 18:58   ` Antony T Curtis
2004-07-08 19:05   ` Julian Seward
2004-07-08 19:47   ` Jim C. Brown
2004-07-08 18:54 ` [Qemu-devel] " Antony T Curtis
2004-07-08 19:36   ` Jim C. Brown
2004-07-08 20:31     ` Jernej Simončič
2004-07-08 21:04       ` Jim C. Brown
2004-07-08 22:37         ` Jernej Simončič
2004-07-08 22:57           ` Jim C. Brown
2004-07-09  0:15           ` [Qemu-devel] RFC for new features (Console under Windows) Filip Navara
2004-07-08 23:40         ` OT: Re: [Qemu-devel] RFC for new features Antony T Curtis
2004-07-08 19:45   ` Jocelyn Mayer
2004-07-08 19:00 ` Karel Gardas
2004-07-08 21:44   ` vaise
2004-07-08 19:30 ` Jean-Michel POURE
2004-07-08 19:48 ` Brad Watson
2004-07-08 21:37 ` Jan Dittmer
2004-07-08 22:24 ` malc
2004-07-08 19:35   ` Jim C. Brown
2004-07-09 20:27 ` [Qemu-devel] " Emmanuel Charpentier
2004-07-09 22:13   ` Antony T Curtis
2004-07-10  0:38     ` Derek Fawcus
2004-07-10  2:44     ` [Qemu-devel] 3Dfx... Just guessing Natalia Portillo
2004-07-10 13:06       ` Fabrice Bellard
2004-07-10 20:41         ` Natalia Portillo
2004-07-11 21:20           ` Ishwar Rattan
2004-07-11 22:42             ` Natalia Portillo
2004-07-11  1:10       ` Jim C. Brown
2004-07-11 11:16         ` Gianni Tedesco
2004-07-11  4:45     ` Re[2]: [Qemu-devel] Re: RFC for new features Igor Shmukler
2004-07-09 21:51 ` [Qemu-devel] (Before) " Hetz Ben Hamo
2004-07-09  9:50   ` Johannes Schindelin
2004-07-10 11:49     ` Hetz Ben Hamo [this message]
2004-07-09 13:25       ` [Qemu-devel] plugins Lionel Ulmer
2004-07-10 15:23         ` Hetz Ben Hamo
2004-07-09 13:35       ` Bartosz Fabianowski
2004-07-09 13:48         ` Gianni Tedesco
2004-07-09 13:39       ` Gianni Tedesco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40EFD7E2.7000607@witch.dyndns.org \
    --to=hetz@witch.dyndns.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).