Re: HID vendor access from user space

From: Jiri Kosina <jkosina@suse.cz>
To: Nestor Lopez Casado <nlopezcasad@logitech.com>
Cc: David Herrmann <dh.herrmann@gmail.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
	Olivier Gay <ogay@logitech.com>,
	Benjamin Tissoires <benjamin.tissoires@gmail.com>,
	Mathieu Meisser <mmeisser@logitech.com>
Subject: Re: HID vendor access from user space
Date: Wed, 16 Apr 2014 16:53:12 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1404161649540.15539@pobox.suse.cz> (raw)
In-Reply-To: <CAE7qMroYKj0rQQ32JMsp-myrESg5V0tkXF2JukhP4aauPapfcQ@mail.gmail.com>

On Tue, 15 Apr 2014, Nestor Lopez Casado wrote:

> > Frankly, I'd really like to avoid any parsing (deciding about collections)
> > whatsoever around hidraw, as that was the whole point of creating it in
> > parallel to hiddev was simply 'no parsing, raw access'.
> 
> We should avoid naming the new nodes "hidrawX" they could be
> "hidvendorX" for instance, or it could also be "hidcolX" where col
> stands for collection. We will be moving the "raw" one level down.

I am still having trouble seeing how this would work together with current 
hidraw.

In your proposal, there will be both hidrawX and hidcolX existing in 
parallel, right? Who will be deciding what goes to hidcolX instead of 
hidrawX? One of the pain points would be -- /dev/hidrawX will have to stay 
anyway for compatibility reasons, so we can't just divide it to multiple 
/dev/hidcolX all of a sudden and never look back.

-- 
Jiri Kosina
SUSE Labs