Re: [BUG?] hid-core.c: hid->name = dev->manufacturer + dev->product ... why not + dev->serial?

From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Melchior FRANZ <melchior.franz@gmail.com>
Cc: linux-input@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Dima Zavin <dmitriyz@google.com>,
	Jonathan Cameron <jic23@cam.ac.uk>,
	LKML <linux-kernel@vger.kernel.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Amit Kucheria <amit.kucheria@verdurent.com>,
	Jean Delvare <khali@linux-fr.org>, Greg KH <greg@kroah.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-iio@vger.kernel.org
Subject: Re: [BUG?] hid-core.c: hid->name = dev->manufacturer + dev->product ... why not + dev->serial?
Date: Tue, 9 Mar 2010 10:41:27 -0800	[thread overview]
Message-ID: <20100309184127.GE19814@core.coreip.homeip.net> (raw)
In-Reply-To: <201003091342.20273@rk-nord.at>

On Tue, Mar 09, 2010 at 01:42:20PM +0100, Melchior FRANZ wrote:
> 
> > Nevertheless serials are exported in sysfs ('uniq' attribute). Also udev
> > can give persistent names device nodes based on physocal connection,
> > serial numbers, etc.
> 
> It's not much fun to use all sorts of additional Linux specific interfaces,
> because the responsible one doesn't do its job.
> 

Have you considered the fact that maybe you not using the
right interface? The legacy joystick interface (with all its warts like
"replaying" the button state, in-kernel scaling and defuzzing, etc.) is
not what I would think a good general-purpose data acquisition
interface.

FWIW evdev does provide access to serial numbers (EVIOCGUNIQ) but even
that in my opinion is not the proper interface, for the reasons I
mentioned in my previous email.

You need to work with guys at linux-iio@vger.kernel.org (which stands
for Industrial I/O which is exactly what you are working with).

-- 
Dmitry