From: Stefan Weil <weil@mail.berlios.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] eepro100: Add more i825xx devices
Date: Tue, 06 Oct 2009 18:29:56 +0200 [thread overview]
Message-ID: <4ACB7084.6000609@mail.berlios.de> (raw)
In-Reply-To: <4ACA40CB.8070604@codemonkey.ws>
Anthony Liguori schrieb:
> Stefan Weil wrote:
>> Anthony, you asked me to send my maintainer version from
>> git://repo.or.cz/qemu/ar7.git
>> in small patches. Of course, the final goal is to have devices which
>> work.
>>
>> To have a list of devices which should be supported helps other
>> people who want
>> to contribute to eepro100.c. They won't write code just for i82557c
>> if the same
>> code should be applied to i82557[ab] as well, for example.
>>
>
> You can do that with comments instead of exposing broken devices to an
> end-user.
>
> Regards,
>
> Anthony Liguori
>
1. The new devices are not exposed to end-users, at least not for the
moment.
2. Many qemu devices are more or less "broken". This is quite normal for an
emulation, because developers of those emulations only have limited
documentation / resources / testing capabilities.
Many users of qemu don't expect a perfect system, and those who do will
stick to those devices which work for them.
So a reasonable way might be to expose many devices to end-users, but
to classify them as stable / testing / experimental (like it is done for the
host and target support).
Regards
Stefan Weil
next prev parent reply other threads:[~2009-10-06 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 11:02 [Qemu-devel] [PATCH] eepro100: Add more i825xx devices Stefan Weil
2009-10-05 13:22 ` Anthony Liguori
2009-10-05 18:05 ` Stefan Weil
2009-10-05 18:54 ` Anthony Liguori
2009-10-06 16:29 ` Stefan Weil [this message]
2009-10-06 19:03 ` Anthony Liguori
2009-10-06 20:53 ` Stefan Weil
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=4ACB7084.6000609@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=anthony@codemonkey.ws \
--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).