From: "Dmitry Torokhov" <dtor@insightbb.com>
To: "Zephaniah E. Hull" <warp@aehallh.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org,
"Marcelo Tosatti" <mtosatti@redhat.com>
Subject: Re: [RFC] OLPC tablet input driver, take two.
Date: Mon, 11 Sep 2006 15:01:35 -0400 [thread overview]
Message-ID: <d120d5000609111201x6d901d2do5d3c2eb934930e4f@mail.gmail.com> (raw)
In-Reply-To: <20060911182733.GR4181@aehallh.com>
On 9/11/06, Zephaniah E. Hull <warp@aehallh.com> wrote:
> On Sun, Sep 10, 2006 at 06:19:31PM -0400, Dmitry Torokhov wrote:
> > >
> > > @@ -616,6 +617,15 @@ static int psmouse_extensions(struct psm
> > > */
> > > max_proto = PSMOUSE_IMEX;
> > > }
> > > + ps2_command(&psmouse->ps2dev, NULL, PSMOUSE_CMD_RESET_DIS);
> >
> > Do we have to do 2nd reset here? Plus logic seems a bit fuzzy here -
> > if ALPS is detected but initizliztion fails it will start OLPC detection
> > which is probably not what you wanted...
>
> Reset is _probably_ not necessary, I'll verify.
>
> However the logic is the same as for all the others, if init succeeds,
> it returns PSMOUSE_ALPS, if it doesn't then it continues on to the next,
> which happens to be olpc, admittedly it would be more obvious that it's
> doing the same thing if it was in its own if, but.
Not exactly. We have 2 types of protocols - some have only detect,
others have both detect and init. For protocols that have both detect
and init we expect detect to reliably identify whether the device is
of given type or not and once detect succeeds we do not try to probe
for other speciality protocols. For example if alps_detect succeeds
but alps_init fails we won't try Genius detection (we will only try
standard imex, exps and bare) and we should not try OLPC detection
either.
--
Dmitry
next prev parent reply other threads:[~2006-09-11 19:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 7:33 [RPC] OLPC tablet input driver Zephaniah E. Hull
2006-08-29 8:10 ` Arjan van de Ven
2006-08-29 8:44 ` Zephaniah E. Hull
2006-08-29 12:29 ` Dmitry Torokhov
2006-08-30 4:45 ` Greg KH
2006-08-29 8:55 ` Komal Shah
2006-08-29 10:40 ` Zephaniah E. Hull
2006-08-29 12:26 ` Dmitry Torokhov
2006-08-29 9:00 ` Komal Shah
2006-08-29 12:53 ` Dmitry Torokhov
2006-08-29 14:35 ` Zephaniah E. Hull
2006-08-29 15:12 ` Dmitry Torokhov
2006-09-10 20:10 ` [RFC] OLPC tablet input driver, take two Zephaniah E. Hull
2006-09-10 22:19 ` Dmitry Torokhov
2006-09-11 18:27 ` Zephaniah E. Hull
2006-09-11 19:01 ` Dmitry Torokhov [this message]
2006-09-11 19:03 ` Zephaniah E. Hull
2006-09-11 19:02 ` [RFC] OLPC tablet input driver, take three Zephaniah E. Hull
2006-09-11 19:10 ` Dmitry Torokhov
2006-09-12 19:39 ` Zephaniah E. Hull
2006-09-12 19:58 ` Dmitry Torokhov
2006-11-08 12:04 ` [RPC] OLPC tablet input driver Vojtech Pavlik
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=d120d5000609111201x6d901d2do5d3c2eb934930e4f@mail.gmail.com \
--to=dtor@insightbb.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=warp@aehallh.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
all inboxes | Powered by JetHome®