From: Vojtech Pavlik <vojtech@suse.cz>
To: Shaun Jackman <sjackman@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Elo touch panel
Date: Wed, 8 Feb 2006 09:51:24 +0100 [thread overview]
Message-ID: <20060208085124.GA4078@suse.cz> (raw)
In-Reply-To: <7f45d9390602071541n65693ae5m7428d59dedcd5ae5@mail.gmail.com>
On Tue, Feb 07, 2006 at 04:41:16PM -0700, Shaun Jackman wrote:
> There's a bug in inputattach. The SERIO_RS232 constant is completely
> mucking the bits that specify the protocol.
>
> --- inputattach.c- 2006-02-07 14:37:04.000000000 -0700
> +++ inputattach.c 2006-02-07 16:22:07.000000000 -0700
> @@ -455,7 +455,7 @@
> return 1;
> }
>
> - devt = SERIO_RS232 | input_types[type].type | (id << 8) | (extra << 16);
> + devt = input_types[type].type | (id << 8) | (extra << 16);
>
> if(ioctl(fd, SPIOCSTYPE, &devt)) {
> fprintf(stderr, "inputattach: can't set device type\n");
>
> Cheers,
> Shaun
>
> APPENDIX A
>
> You probably know this better than I do, but the .type above is
> misnamed. It should really be .proto. It's impossible, as far as I can
> tell, to specify the type (like SERIO_RS232) with a SPIOCSTYPE call.
It's an incompatibility in a later rework of serio.h/serport.c.
SERIO_RS232 used to be 0x02000000, now the constant isn't shifted up
anymore, which messed up things. Also, the type used to be possible to
set, but I don't think that needs to be fixed, since there are so far no
ttys that'd need a different serio type.
I'll apply your fix to inpuatttach. Thanks for spotting the bug.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2006-02-08 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7f45d9390602061830k6b984ban6fb302a3089cac6c@mail.gmail.com>
[not found] ` <20060207081415.GA6731@suse.cz>
2006-02-07 23:41 ` Elo touch panel Shaun Jackman
2006-02-08 8:51 ` Vojtech Pavlik [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=20060208085124.GA4078@suse.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sjackman@gmail.com \
/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