From: Oliver Neukum <oneukum@suse.de>
To: Yann Cantin <yann.cantin@laposte.net>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
gregkh@linuxfoundation.org, dmitry.torokhov@gmail.com,
linux-kernel@vger.kernel.org, jikos@suse.cz
Subject: Re: [eBeam PATCH 2/2] input: misc: New USB eBeam input driver.
Date: Wed, 05 Sep 2012 22:10:15 +0200 [thread overview]
Message-ID: <2074509.XlRZ7oGjqX@linux-lqwf.site> (raw)
In-Reply-To: <5047AECE.80409@laposte.net>
On Wednesday 05 September 2012 21:58:06 Yann Cantin wrote:
> As ebeams are the only devices to my knowledge that work that way, i don't think
> a common API can be common, unless we mean an in-kernel generic purpose calibration
> API for input devices (stellar away for me), or a userland one (where should it be
> in the stack ?). Sincerely, this look overkill.
>
> In the other hand, the actual ebeam module transformation feeding events subsys
> works very well and expose straight and usable data to userland (xorg evdev for now,
> and any program that can eat kernel's input data).
OK, I see the problem. You have no other choice.
> ##
>
> I understand the sysfs interface is a problem. Eventually, in last resort, i can reduce
> it to 4 files : pass the 9 matrix parameters as one big string, removing min values. But
> i think this obfuscate the api for a marginal gain.
That would be wrong. The problem is a specific API. If it needs to be done
at all, it better be done as cleanly as possible.
Regards
Oliver
prev parent reply other threads:[~2012-09-05 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 22:52 [eBeam PATCH 0/2] new " Yann Cantin
2012-09-01 22:52 ` [eBeam PATCH 1/2] hid: Blacklist eBeam devices Yann Cantin
2012-09-01 22:52 ` [eBeam PATCH 2/2] input: misc: New USB eBeam input driver Yann Cantin
2012-09-05 7:29 ` Oliver Neukum
2012-09-05 19:58 ` Yann Cantin
2012-09-05 20:10 ` Oliver Neukum [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2074509.XlRZ7oGjqX@linux-lqwf.site \
--to=oneukum@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=yann.cantin@laposte.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®