From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MvCvN-0004wr-CU for qemu-devel@nongnu.org; Tue, 06 Oct 2009 12:30:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MvCvI-0004tG-Nl for qemu-devel@nongnu.org; Tue, 06 Oct 2009 12:30:04 -0400 Received: from [199.232.76.173] (port=54187 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MvCvI-0004t6-IS for qemu-devel@nongnu.org; Tue, 06 Oct 2009 12:30:00 -0400 Received: from moutng.kundenserver.de ([212.227.126.188]:61160) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MvCvH-0006bk-Vh for qemu-devel@nongnu.org; Tue, 06 Oct 2009 12:30:00 -0400 Message-ID: <4ACB7084.6000609@mail.berlios.de> Date: Tue, 06 Oct 2009 18:29:56 +0200 From: Stefan Weil MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] eepro100: Add more i825xx devices References: <1253358129-10347-1-git-send-email-weil@mail.berlios.de> <4AC9F328.3020609@codemonkey.ws> <4ACA355C.1080802@mail.berlios.de> <4ACA40CB.8070604@codemonkey.ws> In-Reply-To: <4ACA40CB.8070604@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: QEMU Developers 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