Re: [virtio-dev] Re: [PATCH] Update virtio input device specification

2018-08-28 Thread Michael S. Tsirkin
On Wed, Jun 20, 2018 at 06:13:35AM +0300, Michael S. Tsirkin wrote: > On Thu, Apr 06, 2017 at 03:21:26PM +0200, Gerd Hoffmann wrote: > > Hi, > > > > > The downside is that this is hard to specify formally, the same way we > > > do other devices. Say we do that and point to a fixed version of the

Re: [virtio-dev] Re: [PATCH] Update virtio input device specification

2018-06-19 Thread Michael S. Tsirkin
On Thu, Apr 06, 2017 at 03:21:26PM +0200, Gerd Hoffmann wrote: > Hi, > > > The downside is that this is hard to specify formally, the same way we > > do other devices. Say we do that and point to a fixed version of the > > relevant Linux headers and the headers evolve and add or change > > somet

[virtio-dev] Re: [PATCH] Update virtio input device specification

2017-04-06 Thread Ladi Prosek
On Thu, Apr 6, 2017 at 2:25 PM, Michael S. Tsirkin wrote: > On Thu, Apr 06, 2017 at 02:03:32PM +0200, Ladi Prosek wrote: >> >> >> \item[VIRTIO_INPUT_CFG_PROP_BITS] >> >> >> -\field{subsel} is not used and MUST be zero. >> >> >> +\field{subsel} is zero. >> >> >> Returns input properties (INPUT_PR

[virtio-dev] Re: [PATCH] Update virtio input device specification

2017-04-06 Thread Gerd Hoffmann
Hi, > The downside is that this is hard to specify formally, the same way we > do other devices. Say we do that and point to a fixed version of the > relevant Linux headers and the headers evolve and add or change > something. Then we would either go change the spec to be in sync with > the head

[virtio-dev] Re: [PATCH] Update virtio input device specification

2017-04-06 Thread Michael S. Tsirkin
On Thu, Apr 06, 2017 at 02:03:32PM +0200, Ladi Prosek wrote: > >> >> \item[VIRTIO_INPUT_CFG_PROP_BITS] > >> >> -\field{subsel} is not used and MUST be zero. > >> >> +\field{subsel} is zero. > >> >> Returns input properties (INPUT_PROP_*) of the device, in > >> >> \field{u.bitmap}. > >> >> > >> >

[virtio-dev] Re: [PATCH] Update virtio input device specification

2017-04-06 Thread Ladi Prosek
On Thu, Apr 6, 2017 at 12:34 AM, Michael S. Tsirkin wrote: > On Wed, Apr 05, 2017 at 02:21:06PM +0200, Ladi Prosek wrote: >> Apologies for the delay. >> >> On Fri, Mar 24, 2017 at 9:55 PM, Michael S. Tsirkin wrote: >> > On Fri, Mar 24, 2017 at 11:17:59AM +0100, Ladi Prosek wrote: >> >> * added VI

[virtio-dev] Re: [PATCH] Update virtio input device specification

2017-04-05 Thread Michael S. Tsirkin
On Wed, Apr 05, 2017 at 02:21:06PM +0200, Ladi Prosek wrote: > Apologies for the delay. > > On Fri, Mar 24, 2017 at 9:55 PM, Michael S. Tsirkin wrote: > > On Fri, Mar 24, 2017 at 11:17:59AM +0100, Ladi Prosek wrote: > >> * added VIRTIO_INPUT_CFG_ID_DEVIDS / virtio_input_devids > >> * added normat

[virtio-dev] Re: [PATCH] Update virtio input device specification

2017-04-05 Thread Ladi Prosek
Apologies for the delay. On Fri, Mar 24, 2017 at 9:55 PM, Michael S. Tsirkin wrote: > On Fri, Mar 24, 2017 at 11:17:59AM +0100, Ladi Prosek wrote: >> * added VIRTIO_INPUT_CFG_ID_DEVIDS / virtio_input_devids >> * added normative statements and moved them all to >> \devicenormative and \drivernor

[virtio-dev] Re: [PATCH] Update virtio input device specification

2017-03-24 Thread Michael S. Tsirkin
On Fri, Mar 24, 2017 at 11:17:59AM +0100, Ladi Prosek wrote: > * added VIRTIO_INPUT_CFG_ID_DEVIDS / virtio_input_devids > * added normative statements and moved them all to > \devicenormative and \drivernormative sections > * minor tweaks > > Signed-off-by: Ladi Prosek Thanks for taking this u