From: "Natalia Portillo" <claunia@claunia.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] (Before) RFC for new features
Date: Fri, 09 Jul 2004 01:59:10 +0000 [thread overview]
Message-ID: <E1BixNu-0005Fo-OR@lists.gnu.org> (raw)
* 1 Chipset (Intel Natoma)
We should have more?
If anyone can put more, great!
> -----Mensaje original-----
> De: qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org
> [mailto:qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org]
> En nombre de Hetz Ben Hamo
> Enviado el: viernes, 09 de julio de 2004 22:51
> Para: qemu-devel@nongnu.org
> Asunto: [Qemu-devel] (Before) RFC for new features
>
> 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
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next reply other threads:[~2004-07-09 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 1:59 Natalia Portillo [this message]
2004-07-10 15:37 ` [Qemu-devel] (Before) RFC for new features 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 14:03 ` [Qemu-devel] " Fabrice Bellard
2004-07-10 14:47 ` Antony T Curtis
2004-07-10 14:57 ` Fabrice Bellard
2004-07-10 20:53 ` [Qemu-devel] (Before) " Hetz Ben Hamo
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 18:14 [Qemu-devel] " Fabrice Bellard
2004-07-09 21:51 ` [Qemu-devel] (Before) " Hetz Ben Hamo
2004-07-09 9:50 ` Johannes Schindelin
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=E1BixNu-0005Fo-OR@lists.gnu.org \
--to=claunia@claunia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.