From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [PATCH v4] Add virtio-input driver. Date: Wed, 25 Mar 2015 13:51:43 +1030 Message-ID: <877fu5iwxk.fsf@rustcorp.com.au> References: <1427198927-1745-1-git-send-email-kraxel@redhat.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: In-Reply-To: <1427198927-1745-1-git-send-email-kraxel@redhat.com> To: virtio-dev@lists.oasis-open.org, virtualization@lists.linux-foundation.org Cc: mst@redhat.com, David Herrmann , Dmitry Torokhov , Gerd Hoffmann , open list , "open list:ABI/API" , Vojtech Pavlik List-Id: linux-api@vger.kernel.org Gerd Hoffmann writes: > virtio-input is basically evdev-events-over-virtio, so this driver isn't > much more than reading configuration from config space and forwarding > incoming events to the linux input layer. > > Signed-off-by: Gerd Hoffmann Is the input layer sane? I've never dealt with it, so I don't know. What's it used for? Imagine a future virtio standard which incorporates this. And a Windows or FreeBSD implementation of the device and or driver. How ugly would they be? Thanks, Rusty. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752207AbbCYEKc (ORCPT ); Wed, 25 Mar 2015 00:10:32 -0400 Received: from ozlabs.org ([103.22.144.67]:38896 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751224AbbCYEK0 (ORCPT ); Wed, 25 Mar 2015 00:10:26 -0400 From: Rusty Russell To: Gerd Hoffmann , virtio-dev@lists.oasis-open.org, virtualization@lists.linux-foundation.org Cc: mst@redhat.com, David Herrmann , Dmitry Torokhov , Gerd Hoffmann , open list , "open list\:ABI\/API" , "Vojtech Pavlik" Subject: Re: [PATCH v4] Add virtio-input driver. In-Reply-To: <1427198927-1745-1-git-send-email-kraxel@redhat.com> References: <1427198927-1745-1-git-send-email-kraxel@redhat.com> User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Wed, 25 Mar 2015 13:51:43 +1030 Message-ID: <877fu5iwxk.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Gerd Hoffmann writes: > virtio-input is basically evdev-events-over-virtio, so this driver isn't > much more than reading configuration from config space and forwarding > incoming events to the linux input layer. > > Signed-off-by: Gerd Hoffmann Is the input layer sane? I've never dealt with it, so I don't know. What's it used for? Imagine a future virtio standard which incorporates this. And a Windows or FreeBSD implementation of the device and or driver. How ugly would they be? Thanks, Rusty.