qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hetz Ben Hamo <hetz@witch.dyndns.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] (Before) RFC for new features
Date: Sat, 10 Jul 2004 00:51:19 +0300	[thread overview]
Message-ID: <40EF1357.1000600@witch.dyndns.org> (raw)
In-Reply-To: <40ED8EF0.1040501@bellard.org>

Fabrice Bellard wrote:
> Hi,
> 
> As porting the SDL version to other OSes than Linux seems to become an 
> important issue, I plan to add the following features in the next days:

I would like to raise an issue which I'm not sure if it was looked closely..

Lets see what do we have today:

* 3 Busses (ISA, ISA PnP, PCI)
* 4 Processors (Pentium Pro, Arm, PPC, Sparc)
* 4 Network cards (NE2000 ISA, AMD PCNet, NE2000 PCI, 3COM PnP ISA)
* 2 Graphics cards (VESA, Cirrus Logic)
* 2 Bioses (PPC BIOS, Generic Bochs/QEMU BIOS)
* 2 hard drive formats (RAW, COW)

And I'm sure I have forgotten few things, not mentioning QEMU is not 
that publicallyy published (wait for Slashdot effect)..

I think that something needed here: A plugin mechanism.

What I was thinking that QEMU missing is a way that upon running QEMU 
(either first time or doing a first scan), it should "scan" for new 
hardware and register them as plugins (with depenedencies, so you cannot 
use PPC BIOS with Pentium Pro processor ;) ). That way a new plugin 
(either open or closed source) can register itself and a user can simply 
use it without having to configure everything..

The method I was thinking was something like Xine player uses when 
initializing the player..

Fabrice, others, what do you think about it?

Thanks,
Hetz

  parent reply	other threads:[~2004-07-08 21:53 UTC|newest]

Thread overview: 49+ 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 ` Hetz Ben Hamo [this message]
2004-07-09  9:50   ` [Qemu-devel] (Before) " Johannes Schindelin
2004-07-10 11:49     ` [Qemu-devel] plugins Hetz Ben Hamo
2004-07-09 13:25       ` 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
  -- strict thread matches above, loose matches on Subject: below --
2004-07-09  1:59 [Qemu-devel] (Before) RFC for new features Natalia Portillo
2004-07-10 15:37 ` Hetz Ben Hamo
2004-07-09 17:23   ` Natalia Portillo
2004-07-09 17:32   ` Antony T Curtis
2004-07-09 17:57     ` Natalia Portillo
2004-07-09 20:42       ` Jim C. Brown
2004-07-10  2:41         ` Natalia Portillo
2004-07-10 13:10           ` Fabrice Bellard
2004-07-10 20:53         ` Hetz Ben Hamo

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=40EF1357.1000600@witch.dyndns.org \
    --to=hetz@witch.dyndns.org \
    --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).