public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Peter Osterlund <petero2@telia.com>,
	Luca Bigliardi <shammash@artha.org>,
	linux-kernel@vger.kernel.org
Subject: Re: request for opinion on synaptics, adb and powerpc
Date: Sat, 7 Jan 2006 19:40:24 +0100	[thread overview]
Message-ID: <20060107184024.GA11183@corona.suse.cz> (raw)
In-Reply-To: <200601071104.53188.dtor_core@ameritech.net>

On Sat, Jan 07, 2006 at 11:04:52AM -0500, Dmitry Torokhov wrote:
> On Saturday 07 January 2006 03:25, Vojtech Pavlik wrote:
> > 
> > If a relative mode is an absolute must, then a kernel option is IMO
> > sufficient (we have psmouse.proto=imps for the classic PS/2 Synaptics
> > pads), although a sysfs attribute would likely be better.
> > 
> 
> Just FYI, writing into /sys/bus/serio/devices/serioX/protcol allows
> swicthing ptorocol dynamically (this involves teardown of old input
> device and creation of a new one).

I know, but this will not be possible if the Synaptics pad is connected
over ADB, which is the case I believe we are discussing here. 

On the other hand, if it's just PS/2 over ADB, a serio driver instead of
an input driver would make more sense.

> > In theory, we could use EV_SYN, SYN_CONFIG for notifying applications
> > that the device has changed its capabilities, but a
> > disconnect/recreation will work better, since no applications support
> > the SYN_CONFIG notification ATM.
> 
> I could see SYN_CONFIG being used to signal changes in limits (like min
> and max X coordinates) but not to basic device capabilities.

Yes, that's probably more sensible.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2006-01-07 18:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060106231301.GG4732@kamaji.shammash.lan>
2006-01-07  0:25 ` request for opinion on synaptics, adb and powerpc Peter Osterlund
2006-01-07  0:51   ` Benjamin Herrenschmidt
2006-01-07  4:17     ` Dmitry Torokhov
2006-01-07  4:33       ` Benjamin Herrenschmidt
2006-01-07  4:36         ` Dmitry Torokhov
2006-01-07  4:44           ` Benjamin Herrenschmidt
2006-01-07  4:46             ` Dmitry Torokhov
2006-01-07  5:02               ` Dmitry Torokhov
2006-01-07  5:49               ` Benjamin Herrenschmidt
2006-01-07  8:25         ` Vojtech Pavlik
2006-01-07 16:04           ` Dmitry Torokhov
2006-01-07 18:40             ` Vojtech Pavlik [this message]
2006-01-07 22:15               ` Benjamin Herrenschmidt

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=20060107184024.GA11183@corona.suse.cz \
    --to=vojtech@suse.cz \
    --cc=benh@kernel.crashing.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=shammash@artha.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