[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (VIRTIO-96) Assign device id to virtio input
[ https://tools.oasis-open.org/issues/browse/VIRTIO-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Tsirkin updated VIRTIO-96: ---------------------------------- Description: I'd like to have a virtio device id assigned for the virtio input device I'm working on. The virtio input device basically sends linux input layer events (evdev) over virtio. More info: http://www.kraxel.org/cgit/virtio-spec/log/?h=virtio-input Kernel code: http://www.kraxel.org/cgit/linux/log/?h=virtio-input Qemu code (has unrelated qemu input code bits too): http://www.kraxel.org/cgit/qemu/log/?h=rebase/input-wip > Assign device id to virtio input > -------------------------------- > > Key: VIRTIO-96 > URL: https://tools.oasis-open.org/issues/browse/VIRTIO-96 > Project: OASIS Virtual I/O Device (VIRTIO) TC > Issue Type: Improvement > Affects Versions: virtio 1.0 csprd02 > Environment: Gerd Hoffmann kraxel@redhat.com > Reporter: Michael Tsirkin > Priority: Minor > > I'd like to have a virtio device id assigned for the virtio input device I'm working on. > The virtio input device basically sends linux input layer events (evdev) over virtio. > More info: > http://www.kraxel.org/cgit/virtio-spec/log/?h=virtio-input > Kernel code: > http://www.kraxel.org/cgit/linux/log/?h=virtio-input > Qemu code (has unrelated qemu input code bits too): > http://www.kraxel.org/cgit/qemu/log/?h=rebase/input-wip -- This message was sent by Atlassian JIRA (v6.1.1#6155)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]