Hi,
>> diff --git a/qapi-schema.json b/qapi-schema.json
>> index 7e5c8c2..d833385 100644
>> --- a/qapi-schema.json
>> +++ b/qapi-schema.json
>> @@ -3036,7 +3036,8 @@
>> { 'type': 'ChardevFile', 'data': { '*in' : 'ChardevFileSource',
>> 'out' : 'ChardevFileSource' } }
>>
>> -{ 'enum': 'ChardevPortKind', 'data': [ 'tty' ] }
>> +{ 'enum': 'ChardevPortKind', 'data': [ 'tty',
>> + 'serial' ] }
>
> Can we just use one name, either tty or serial?
Both are in use today, 'serial' on windows and 'tty' on linux.
'tty' on windows doesn't make sense.
'serial' on linux does, but it actually is a subset of 'tty' and needs
no special care, thats why I simply aliased it for convenience.
We could switch to use 'serial' only for qmp, but I think that will be
confusing as the old 'tty' name will have to stay for -chardev.
We could just not do the alias thing and continue to use the 'serial' on
windows + 'tty' on linux (posix) scheme.
> And for the QemuOpts
> version, alias them too.
Did that ...
>> #ifdef HAVE_CHARDEV_TTY
>> { .name = "tty", .open = qemu_chr_open_tty },
>> + { .name = "serial", .open = qemu_chr_open_tty },
>> { .name = "pty", .open = qemu_chr_open_pty },
>> #endif
... here.
cheers,
Gerd
