Linux Input/HID development
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web.de>
To: linux-input@vger.kernel.org
Subject: serial touchscreen and inputattach
Date: Sun, 15 Jun 2008 21:01:09 +0200	[thread overview]
Message-ID: <200806152101.10156.markus.heidelberg@web.de> (raw)

Hello,

I'm currently working on a serial touchscreen driver and have some questions.

What's the rule for creating a new name for serio protocol in serio.h for use
in serio_device_id.proto and input_dev.id.vendor? Can I just take a free
number? I guess then I should take the next one (currently 0x37 after
SERIO_ZHENHUA), however there are some gaps in the list.

Is there an official version of inputattach? I found different sources. The
last change at [1] is about 2 years ago. At [2] there is a broken CVS link to
[1]. The inputattach tool in buildroot's tslib package is derived from [1] with
some minor changes. The inputattach from Debian's joystick package is derived
from a three years old version of [1], the tool from Gentoo's joystick package
is the same as in [1].

So it seems as if [1] is quite official, because everything is pointing to it.
But there is another inputattach at [3] with a reworked code base, which is
only 1 year old and supports some more devices, mainly touchscreens.

Or is there another preferred way beside inputattach to bind the touchscreen to
its driver and inputattach is obsolete?

[1] http://linuxconsole.cvs.sourceforge.net/linuxconsole/ruby/utils/
[2] http://atrey.karlin.mff.cuni.cz/~vojtech/input/
[3] http://kernel.org/pub/linux/kernel/people/dtor/

Markus


             reply	other threads:[~2008-06-15 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-15 19:01 Markus Heidelberg [this message]
2008-06-15 19:57 ` serial touchscreen and inputattach Peter Korsgaard
2008-06-15 20:16   ` Markus Heidelberg

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=200806152101.10156.markus.heidelberg@web.de \
    --to=markus.heidelberg@web.de \
    --cc=linux-input@vger.kernel.org \
    /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