public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stelian Pop <stelian@popies.net>
To: Peter Osterlund <petero2@telia.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Vojtech Pavlik <vojtech@suse.cz>,
	Frank Arnold <frank@scirocco-5v-turbo.de>
Subject: Re: [PATCH] Apple USB Touchpad driver (new)
Date: Mon, 11 Jul 2005 12:06:25 +0200	[thread overview]
Message-ID: <1121076385.12619.5.camel@localhost.localdomain> (raw)
In-Reply-To: <m37jfzr4oi.fsf@telia.com>

Le dimanche 10 juillet 2005 à 00:32 +0200, Peter Osterlund a écrit :
> Stelian Pop <stelian@popies.net> writes:
> 
> > +Synaptics re-detection problems:
> > +--------------------------------
> > +
> > +The synaptics X11 driver tries to re-open the touchpad input device file
> > +(/dev/input/eventX) each time you change from text mode back to X11. If the
> > +input device file does not exist at this precise moment, the synaptics driver
> > +will give up searching for a touchpad, permanently. You will need to restart
> > +X11 if you want to reissue a scan.
> 
> I think this particular problem is fixed by the following patch to the
> X driver:
> 
> --- synaptics.c.old	2005-07-10 00:09:02.000000000 +0200
> +++ synaptics.c	2005-07-10 00:09:12.000000000 +0200
> @@ -524,6 +524,11 @@
>  
>      local->fd = xf86OpenSerial(local->options);
>      if (local->fd == -1) {
> +	xf86ReplaceStrOption(local->options, "Device", "");
> +	SetDeviceAndProtocol(local);
> +	local->fd = xf86OpenSerial(local->options);
> +    }
> +    if (local->fd == -1) {
>  	xf86Msg(X_WARNING, "%s: cannot open input device\n", local->name);
>  	return !Success;
>      }

It does indeed fix the problem.

I removed that section from the documentation, as I assume you will
integrate this patch in future synaptics releases (and it wasn't anyway
a big problem for users, just for developers).

> 
> > +static int atp_calculate_abs(int *xy_sensors, int nb_sensors, int fact) {
> 
> I think this CodingStyle violation is quite annoying, because it
> prevents emacs from finding the beginning of the function. It should
> be written like this:

Indeed, that one slipped over, but this didn't prevent vim from finding
the beginning of the function :)

Thanks,

Stelian.
-- 
Stelian Pop <stelian@popies.net>


      parent reply	other threads:[~2005-07-11 10:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 10:17 [PATCH] Apple USB Touchpad driver (new) Stelian Pop
2005-07-08 11:18 ` Johannes Berg
2005-07-08 12:10   ` Stelian Pop
2005-07-09 19:13     ` Vojtech Pavlik
2005-07-09 22:48       ` Peter Osterlund
2005-07-10 12:04         ` Vojtech Pavlik
2005-07-11  0:15           ` Peter Osterlund
2005-07-11 10:39             ` Stelian Pop
2005-07-11 11:00               ` Vojtech Pavlik
2005-07-11 11:08                 ` Stelian Pop
2005-07-11 11:21                   ` Vojtech Pavlik
2005-07-11 12:47                     ` Stelian Pop
2005-07-11 13:35                       ` Stelian Pop
2005-07-12  9:05                     ` Stelian Pop
2005-07-12 14:13                       ` Dmitry Torokhov
2005-07-12 14:33                         ` Stelian Pop
2005-07-12 14:47                           ` Dmitry Torokhov
2005-07-12 18:13                             ` Vojtech Pavlik
2005-07-12 19:21                               ` Stelian Pop
     [not found]               ` <20050711035244.115067ac.akpm@osdl.org>
2005-07-11 11:04                 ` Stelian Pop
2005-07-11 13:25                   ` Peter Osterlund
2005-07-11 20:44                   ` Lee Revell
2005-07-11 20:54                     ` Stelian Pop
2005-07-11 13:48               ` Peter Osterlund
2005-07-11 10:47             ` Vojtech Pavlik
2005-07-09 22:32     ` Peter Osterlund
2005-07-10 11:58       ` Vojtech Pavlik
2005-07-11 10:06       ` Stelian Pop [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=1121076385.12619.5.camel@localhost.localdomain \
    --to=stelian@popies.net \
    --cc=frank@scirocco-5v-turbo.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=vojtech@suse.cz \
    /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