[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100309184127.GE19814@core.coreip.homeip.net>
Date: Tue, 9 Mar 2010 10:41:27 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Melchior FRANZ <melchior.franz@...il.com>
Cc: linux-input@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Dima Zavin <dmitriyz@...gle.com>,
Jonathan Cameron <jic23@....ac.uk>,
LKML <linux-kernel@...r.kernel.org>,
Zhang Rui <rui.zhang@...el.com>,
Amit Kucheria <amit.kucheria@...durent.com>,
Jean Delvare <khali@...ux-fr.org>, Greg KH <greg@...ah.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-iio@...r.kernel.org
Subject: Re: [BUG?] hid-core.c: hid->name = dev->manufacturer + dev->product
... why not + dev->serial?
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@...r.kernel.org (which stands
for Industrial I/O which is exactly what you are working with).
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists