public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Smietanowski <stesmi@stesmi.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 24/44] Workaround i8042 chips with broken MUX mode
Date: Fri, 19 Mar 2004 15:21:27 +0100	[thread overview]
Message-ID: <405B01E7.5000809@stesmi.com> (raw)
In-Reply-To: <20040319135819.GB658@ucw.cz>

Hi.

> So far on every machine I've got a report from it was caused by BIOS
> emulation of PS/2 mouse using an USB mouse (even when USB mouse wasn't
> present). Compiling the USB modules into the kernel fixes the problem.

Could this have anything to do with the fact that my x86-64 kernel nukes
on startup if USB keyboard/mouse emul is enabled in the BIOS?

This is on an ASUS K8T800 and an MSI K8T800 board.

If you don't know what I'm talking about I'll give more info of course.

// Stefan

  reply	other threads:[~2004-03-19 14:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 18:24 [PATCH 24/44] Workaround i8042 chips with broken MUX mode Dmitry Torokhov
2004-03-18 20:37 ` Vojtech Pavlik
     [not found]   ` <200403190005.36956.dtor_core@ameritech.net>
2004-03-19 13:58     ` Vojtech Pavlik
2004-03-19 14:21       ` Stefan Smietanowski [this message]
2004-03-19 14:30         ` Vojtech Pavlik
2004-03-19 13:56 ` Vojtech Pavlik
2004-03-28  0:29 ` Andries Brouwer
2004-03-28  0:40   ` Dmitry Torokhov
2004-03-28  1:25     ` Andries Brouwer
2004-03-28  3:11       ` Dmitry Torokhov
2004-03-28  7:45     ` Stefan Smietanowski
  -- strict thread matches above, loose matches on Subject: below --
2004-03-16 14:19 [PATCH 23/44] Use __obsolete_setup() in input drivers to warn about obsolete kernel params Vojtech Pavlik
2004-03-16 14:19 ` [PATCH 24/44] Workaround i8042 chips with broken MUX mode 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=405B01E7.5000809@stesmi.com \
    --to=stesmi@stesmi.com \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=vojtech@suse.cz \
    /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