Blue Swirl <blauwir...@gmail.com> wrote:
> On Tue, Feb 1, 2011 at 4:53 PM, Eduardo Habkost <ehabk...@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.
