From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=39913 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PkSzk-0003TF-Iz
	for qemu-devel@nongnu.org; Tue, 01 Feb 2011 22:03:01 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1PkSzj-0006CS-FJ
	for qemu-devel@nongnu.org; Tue, 01 Feb 2011 22:03:00 -0500
Received: from mx1.redhat.com ([209.132.183.28]:55385)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1PkSzj-0006CA-8J
	for qemu-devel@nongnu.org; Tue, 01 Feb 2011 22:02:59 -0500
From: Juan Quintela <quintela@redhat.com>
In-Reply-To: <AANLkTi=Yz2mc6CWQ4e_51KpgLWpx-21z6+RAhS8UvC5m@mail.gmail.com>
	(Blue Swirl's message of "Tue, 1 Feb 2011 18:10:24 +0000")
References: <1296579203-21083-1-git-send-email-ehabkost@redhat.com>
	<AANLkTi=Yz2mc6CWQ4e_51KpgLWpx-21z6+RAhS8UvC5m@mail.gmail.com>
Date: Wed, 02 Feb 2011 04:01:42 +0100
Message-ID: <m3pqrb9m21.fsf@trasno.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Qemu-devel] Re: [PATCH 0/4] fix/add CONFIG_* options for VMWare
	device emulation
Reply-To: quintela@redhat.com
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org

Blue Swirl <blauwirbel@gmail.com> wrote:
> On Tue, Feb 1, 2011 at 4:53 PM, Eduardo Habkost <ehabkost@redhat.com> wrote:
>> Hi,
>>
>> This series makes CONFIG_VMWARE_VGA actually work (today we can't disable the
>> option without getting a build error).
>>
>> It also add two new options: CONFIG_VMMOUSE and CONFIG_VMPORT, for vmmouse.o
>> and vmport.o.
>
> Nack, see the list archives for the discussion.
>
> One way to solve this which would preserve the device model would be
> to add stub devices. For example, hw/vmmouse-stub.c would be:
> void *vmmouse_init(void *m)
> {
>     return NULL;
> }

I read the archives, and I still think that this is a stop backwards.  I
was (one of the much) proposing the feature.

If this features is requested each 3 months for different people, could
it be that really, really, our device model is not good enough?

We have three config files:
- config-host.mak
- config-target.mak
- config-devices.mak

First two have a .h associated file, last one don't have it. And people
is requesting it each 3 months.


Later, Juan.