All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boszormenyi Zoltan <zboszor@pr.hu>
To: "Stephen Kitt" <steve@sk2.org>,
	"Böszörményi Zoltán" <zboszormenyi@sicom.com>
Cc: Vojtech Pavlik <vojtech@suse.com>,
	linuxconsole-dev@lists.sourceforge.net,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] Add support for the egalax serial touchscreen driver
Date: Tue, 15 Dec 2015 20:18:59 +0100	[thread overview]
Message-ID: <567067A3.8080905@pr.hu> (raw)
In-Reply-To: <20151215200630.0a8b5479@heffalump.sk2.org>

Hi,

2015-12-15 20:06 keltezéssel, Stephen Kitt írta:
> Hi,
>
> Thanks for submitting this. I have just a couple of questions...
>
> On Tue, 15 Dec 2015 12:24:32 +0100, Böszörményi Zoltán
> <zboszormenyi@sicom.com> wrote:
>> +static int egalax_init(int fd, unsigned long *id, unsigned long *extra) {
>> +	unsigned char packet_alive_query[3] = { 0x0a, 0x01, 'A' };
>> +	unsigned char packet_fw_ver[3] = { 0x0a, 0x01, 'D' };
>> +	unsigned char packet_ctrl_type[3] = { 0x0a, 0x01, 'E' };
>> +	unsigned char response[128];
>> +
>> +	if (check_egalax_response(fd, packet_alive_query, sizeof(packet_alive_query), response))
>> +		return -1;
>> +
>> +	if (check_egalax_response(fd, packet_fw_ver, sizeof(packet_fw_ver), response))
>> +		return -1;
>> +
>> +	response[(unsigned char)response[1] + 2] = '\0';
>> +	printf("EETI eGalaxTouch firmware: %s\n", &response[3]);
> inputattach is generally silent when everything goes well. I can see how this
> kind of info would be useful though; would you mind simply commenting the
> printf() lines out, and I'll add a verbose mode later on?

Sure, I'll put it under #ifdef 0.

>
>> +
>> +	if (check_egalax_response(fd, packet_ctrl_type, sizeof(packet_ctrl_type), response))
>> +		return -1;
>> +
>> +	response[(unsigned char)response[1] + 2] = '\0';
>> +	printf("EETI eGalaxTouch controller type: %s\n", &response[3]);
> As above.
>
>> +#ifdef SERIO_HAMPSHIRE
>> +{ "--hampshire",   "-ham",         "Hampshire touchscreen",
>> +	B9600, CS8,
>> +	SERIO_HAMPSHIRE,	0x00,   0x00,   0,  NULL },
>> +#endif
> Is this intentional? If so, could you mention it in the commit message?

Yes, it is intentional. I noticed that the SERIO_HAMPSHIRE support
is also missing from inputattach. I don't currently know if the
Hampshire touchscreen needs an init function or not, so it is a
placeholder at the moment. Also, the SERIO_HAMPSHIRE value is
smaller than SERIO_PS2MULT which is unconditionally enabled,
so maybe it doesn't need the #ifdef SERIO_HAMPSHIRE ... #endif
cover at all. I will mention it in the commit message for the v2 patch,
which I will send tomorrow.

Best regards,
Zoltán Böszörményi

--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-12-15 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 11:24 [PATCH] Add support for the egalax serial touchscreen driver Böszörményi Zoltán
2015-12-15 19:06 ` Stephen Kitt
2015-12-15 19:18   ` Boszormenyi Zoltan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-15  9:40 Böszörményi Zoltán

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=567067A3.8080905@pr.hu \
    --to=zboszor@pr.hu \
    --cc=linux-input@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    --cc=steve@sk2.org \
    --cc=vojtech@suse.com \
    --cc=zboszormenyi@sicom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.