All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <alan@redhat.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.62-ac1
Date: Fri, 21 Feb 2003 17:10:50 +0100	[thread overview]
Message-ID: <20030221161050.GA163@elf.ucw.cz> (raw)
In-Reply-To: <200302211153.h1LBrYR12271@devserv.devel.redhat.com>

Hi!

> > > Linux 2.5.62-ac1
> > > o	PC-9800 update			(Osamu Tomita)
> > Thanks!
> > 
> > > o	Toshiba keyboard workaround		(Pavel Machek)
> > This change conflict with PC98 keyboard. Always shows message
> > 'Keyboard glitch detected, ignoring keypress' every keypress.
> > Other machine has no problem?
> 
> I've had no other reports of it triggering wrongly. Thats easy to
> deal with. Pavel can you send me the dmidecode data for the afflicted
> laptop ?

arch/i386/kernel/dmi_scan.c, broken_toshiba_keyboard() is the right
place. DMI data are:

        { broken_toshiba_keyboard, "Toshiba Satellite 4030cdt", { /* Keyboard generates spurious repeats */
                        MATCH(DMI_PRODUCT_NAME, "S4030CDT/4.3"),
                        NO_MATCH, NO_MATCH, NO_MATCH
                        } },
 
							Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2003-02-21 21:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-21  5:37 Linux 2.5.62-ac1 Osamu Tomita
2003-02-21 11:53 ` Alan Cox
2003-02-21 16:10   ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-20 22:33 Alan Cox
2003-02-20 23:05 ` Tomas Szepe
2003-02-20 23:06   ` Alan Cox
2003-02-20 23:09     ` Tomas Szepe
2003-02-20 23:31 ` Steven Cole
2003-02-20 23:57   ` Alan Cox
2003-02-21  1:48     ` Steven Cole
2003-02-21 15:09 ` Adrian Bunk
2003-02-21 15:12 ` Adrian Bunk
2003-02-21 16:31   ` James Simmons
2003-02-23 11:06     ` Geert Uytterhoeven
2003-02-25 16:26       ` James Simmons
2003-02-25 16:28         ` Geert Uytterhoeven

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=20030221161050.GA163@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=alan@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.