Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: parisc-linux@lists.parisc-linux.org
Cc: Andy Walker <andy@puszczka.com>
Subject: Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]
Date: Tue, 9 Mar 2004 22:59:05 +0100	[thread overview]
Message-ID: <200403092259.05202.deller@gmx.de> (raw)
In-Reply-To: <28565.193.161.152.244.1078828435.squirrel@www.puszczka.com>

On Dienstag, 9. März 2004 11:33, Andy Walker wrote:
> I'm just about to give this a try. The reason these weren't enabled is
> that menuconfig was a bit non-intuitive (to me at least). Maybe I was
> just being paranoid, but when I selected ATKBD or MOUSE_PS2 then the GSC
> PS/2 item got closed up and I didn't know whether it was on or off. That
> scared me and I assumed that selecting GSC PS/2 support would enable
> everything else I needed. Compiling now, but I won't be able to test
> until I get home from work and actually get my hands on the keyboard/mouse.

Hi Andy,

I agree, that this behaviour seems somehow little strange. Thibaut Varene
complained too.
But on the other side without this auto-enablement of the GSC PS/2 controller
users maybe enable PS/2 mouse and/or PS/2 keyboard and miss enabling the
GSC PS/2 controller too - with the result, that neither keyboard or mouse would
work when the kernel is booted....

Personally I prefer the automatic enablement. Even on iA32 this is the default now.

Best regards,
Helge

  parent reply	other threads:[~2004-03-09 22:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 11:28 [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34] Andy Walker
2004-03-09  5:36 ` Grant Grundler
2004-03-09 11:27   ` Andy Walker
2004-03-09 21:16     ` Matthew Wilcox
2004-03-09 21:04   ` Matthew Wilcox
2004-03-10  4:59     ` Grant Grundler
2004-03-09 10:03 ` Helge Deller
     [not found]   ` <28565.193.161.152.244.1078828435.squirrel@www.puszczka.com>
2004-03-09 21:59     ` Helge Deller [this message]
2004-03-09 22:21       ` Andy Walker
2004-03-14  7:37   ` [parisc-linux] " Martin Schulze
2004-03-14 15:28     ` M. Grabert
2004-03-14 18:12       ` Martin Schulze
2004-03-14 19:55         ` Helge Deller
2004-03-14 20:28           ` Martin Schulze
2004-03-14 21:19             ` Helge Deller
2004-03-15 17:14               ` [parisc-linux] " Martin Schulze
2004-03-15 19:46                 ` [parisc-linux] " Helge Deller
2004-03-15 20:02                   ` Andy Walker
2004-03-18  9:55                   ` Martin Schulze
2004-03-14 19:48     ` Helge Deller
2004-03-14 20:49       ` [parisc-linux] " Martin Schulze
2004-03-15  0:31         ` Grant Grundler
2004-03-15  8:42           ` Martin Schulze
2004-03-15 15:05             ` Martin Schulze
2004-03-15 22:47               ` Helge Deller
2004-03-14 20:47     ` [parisc-linux] " Martin Schulze
2004-03-14 21:24       ` Helge Deller
  -- strict thread matches above, loose matches on Subject: below --
2004-03-09 11:05 [parisc-linux] " Andy Walker
2004-03-08 11:03 Andy Walker

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=200403092259.05202.deller@gmx.de \
    --to=deller@gmx.de \
    --cc=andy@puszczka.com \
    --cc=parisc-linux@lists.parisc-linux.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