public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gunther.Mayer@t-online.de (Gunther Mayer)
To: Kurt Garloff <garloff@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make psaux reconnect adjustable
Date: Wed, 15 Aug 2001 17:50:11 +0200	[thread overview]
Message-ID: <3B7A9A33.5A649036@t-online.de> (raw)
In-Reply-To: <20010814170306.Q1085@gum01m.etpnet.phys.tue.nl> <Pine.LNX.4.33.0108140954390.1679-100000@penguin.transmeta.com> <20010814232947.A16332@gum01m.etpnet.phys.tue.nl>

Kurt Garloff wrote:
> 
> On Tue, Aug 14, 2001 at 09:58:55AM -0700, Linus Torvalds wrote:
> >  - do we actually need the config switch AT ALL, whether at bootup or not?
> >    What exactly breaks if we just always pass the AA 00 values through?
> >    Apparently nothing ever breaks, which makes me suspect that people are
> >    just being unnecessarily defensive.
> >
> > In short, I'd prefer a patch that just unconditionally removes the code,
> > unless somebody KNOWS that it could break something. That failing, a
> > simple kernel command line option sounds better than more files in /proc.

Linus, no more boot options (and no more files in /proc), please.

Don't push policy on users when there is a perfect, simple and _user-friendly_ solution.

> 
> OK, here come two patches. The first one removes the special PSAUX reconnect
> handling completely. So userspace should handle it. (Which is possible; just
> not implemented in gpm/X11 at this time AFAIK.)
> 
> Second patch reintroduces the special handling again, but does
> * react on AA 00 instead of just AA, thus much less likely breaking other
>   drivers (such as synps2). All PS/2 mouses I could access (about 5
>   different models) produced AA 00, so this seems OK.
> * is disabled by default, and needs to be enabled by the psaux-reconnect
>   boot parameter, like in 2.2.19.

Your patch for "AA 00" is preferable over current state "AA" (<=2.4.8)

ioctl is preferable over sysctl. Aware drivers do "ioctl("/dev/psaux", PS2_TRANSPARENT)".

run-time configuration is preferable over a boot parameter (see above about user-friendliness).

Not breaking current behaviour ("reconnecting 3-byte protocol mice works perfectly") is preferable.

  reply	other threads:[~2001-08-15 15:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 17:27 [PATCH] make psaux reconnect adjustable Andries.Brouwer
2001-08-14  9:57 ` Kurt Garloff
2001-08-14 15:03   ` Kurt Garloff
2001-08-14 16:58     ` Linus Torvalds
2001-08-14 17:35       ` Kurt Garloff
2001-08-14 21:29       ` Kurt Garloff
2001-08-15 15:50         ` Gunther Mayer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-14 21:26 Andries.Brouwer
2001-08-14 18:29 Andries.Brouwer
2001-08-14 19:35 ` Gunther Mayer
2001-08-14 11:12 Andries.Brouwer
2001-08-14 17:10 ` Gunther Mayer
2001-08-14 21:56   ` Kurt Garloff
2001-08-02 16:02 Andries.Brouwer
2001-08-02 16:18 ` Kurt Garloff
     [not found] <no.id>
2001-08-02 15:03 ` Alan Cox
2001-08-02 17:34 ` Alan Cox
2001-08-02 11:55 Andries.Brouwer
2001-08-02  2:21 Kurt Garloff

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=3B7A9A33.5A649036@t-online.de \
    --to=gunther.mayer@t-online.de \
    --cc=garloff@suse.de \
    --cc=linux-kernel@vger.kernel.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