From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: H Hartley Sweeten
<hartleys-3FF4nKcrg1dE2c76skzGb0EOCMrvLtNR@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [Q] i2c-taos-evm bus driver
Date: Tue, 9 Feb 2010 09:16:39 +0100 [thread overview]
Message-ID: <20100209091639.5b6e39a5@hyperion.delvare> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190902152F0E-KURmP/Qoe8Pmp66j18f85VaTQe2KTcn/@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]
Hi Hartley,
Please send i2c-specific questions to the linux-i2c list, as specified
in MAINTAINERS.
On Mon, 8 Feb 2010 18:15:26 -0500, H Hartley Sweeten wrote:
> Is the i2c-taos-evm bus driver broken?
No, it works reasonably fine. I was using it myself no later than one
month ago. Out of curiosity, with which exact evaluation module do you
plan to use it?
> The Documentation says to use the following to tell the kernel that
> the device is on the first serial port:
>
> # inputattach --taos-evm /dev/ttyS0
>
> When I try that I get:
>
> inputattach: invalid mode
>
> I checked the source for inputattach on my system (Debian 5.0) and
> --taos-evm is missing. And I have not been able to locate a newer
> version of the user-space utility.
>
> Should this driver be marked broken?
No. What is broken is input-utils' upstream. I tried submitting patches
2.5 years ago:
http://sourceforge.net/tracker/?group_id=3063&atid=303063
As you can see, nobody took care of them. Apparently I then did not
even bother sending the one adding support for the TAOS EVM.
The patch in question is still applied to the openSUSE version of the
input-utils package. If you have access to the openSUSE build system,
you can see it here:
https://build.opensuse.org/package/view_file?file=input-utils-add-taos-evm-support.patch&package=input-utils&project=openSUSE%3A11.0
In case you don't, I'm attaching it too. I might add it to the patch
tracking system on sourceforge too. Not that I really expect upstream
to pick it in a timely manner, but at least other distributions would
see it and may decide to include it.
Hope that helps,
--
Jean Delvare
[-- Attachment #2: input-utils-add-taos-evm-support.patch --]
[-- Type: text/x-patch, Size: 1113 bytes --]
---
inputattach.c | 6 ++++++
1 file changed, 6 insertions(+)
--- utils.orig/inputattach.c 2007-06-22 10:25:32.000000000 +0200
+++ utils/inputattach.c 2008-05-11 15:41:57.000000000 +0200
@@ -376,6 +376,9 @@ struct input_types input_types[] = {
{ "--elo4002", "-elo6b", B9600, CS8 | CRTSCTS, SERIO_ELO, 1, 0, 0, NULL },
{ "--elo271-140", "-elo4b", B9600, CS8 | CRTSCTS, SERIO_ELO, 2, 0, 0, NULL },
{ "--elo261-280", "-elo3b", B9600, CS8 | CRTSCTS, SERIO_ELO, 3, 0, 0, NULL },
+#ifdef SERIO_TAOSEVM
+{ "--taos-evm", "-taos", B1200, CS8, SERIO_TAOSEVM, 0, 0, 0, NULL },
+#endif
{ "--dump", "-dump", B2400, CS8, 0, 0, 0, 0, dump_init },
{ "", "", 0, 0 }
@@ -421,6 +424,9 @@ int main(int argc, char **argv)
puts(" --elo4002 -elo6b Elo touchscreen (legacy 6-byte protocol)");
puts(" --elo271-140 -elo4b Elo touchscreen (legacy 4-byte protocol)");
puts(" --elo261-280 -elo3b Elo touchscreen (legacy 3-byte protocol)");
+#ifdef SERIO_TAOSEVM
+ puts(" --taos-evm -taos TAOS evaluation module");
+#endif
puts("");
return 1;
}
next parent reply other threads:[~2010-02-09 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BD79186B4FD85F4B8E60E381CAEE190902152F0E@mi8nycmail19.Mi8.com>
[not found] ` <BD79186B4FD85F4B8E60E381CAEE190902152F0E-KURmP/Qoe8Pmp66j18f85VaTQe2KTcn/@public.gmane.org>
2010-02-09 8:16 ` Jean Delvare [this message]
2010-02-09 16:38 ` [Q] i2c-taos-evm bus driver H Hartley Sweeten
[not found] ` <BD79186B4FD85F4B8E60E381CAEE190902152FBE-KURmP/Qoe8Pmp66j18f85VaTQe2KTcn/@public.gmane.org>
2010-02-09 20:42 ` Jean Delvare
[not found] ` <20100209214252.2a01f010-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-02-11 17:12 ` H Hartley Sweeten
[not found] ` <BD79186B4FD85F4B8E60E381CAEE190902153420-KURmP/Qoe8Pmp66j18f85VaTQe2KTcn/@public.gmane.org>
2010-02-11 17:43 ` Dmitry Torokhov
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=20100209091639.5b6e39a5@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=hartleys-3FF4nKcrg1dE2c76skzGb0EOCMrvLtNR@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).