public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Stirling <ian.stirling@mauve.plus.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
	Kim Holviala <kim@holviala.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] psmouse: fix mouse hotplugging
Date: Thu, 22 Apr 2004 23:04:21 +0100	[thread overview]
Message-ID: <40884165.5030407@mauve.plus.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0404221754470.16448@jurand.ds.pg.gda.pl>

Maciej W. Rozycki wrote:
> On Thu, 22 Apr 2004, Horst von Brand wrote:
> 
> 
>>>This patch fixes hotplugging of PS/2 devices on hardware which don't
>>>support hotplugging of PS/2 devices. In other words, most desktop
>>
>>machines.
>>
>>I have seen "hoplugging of mice" fry PS/2 ports, and heard of motherboards
>>killed that way. 
> 
> 
>  For older systems, a fuse would often blow on these ports, which
> depending on the implementation would require a power cycle or a soldering
> iron.  Then one of those PCxx specs from Microsoft required the PS/2 ports
> to support hot-plugging, so chances are it may pretty safe with recent
> equipment.

Even for relatively newer kit, wierd stuff can happen.
I recall one keyboard/athlon 500 system that would reboot 10s after the keyboard
was plugged in, about 1% of the time.
Probably a KBC code bug, but unfixable.

  reply	other threads:[~2004-04-22 22:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22  7:44 [PATCH] psmouse: fix mouse hotplugging Kim Holviala
2004-04-22 15:46 ` Horst von Brand
2004-04-22 16:01   ` Maciej W. Rozycki
2004-04-22 22:04     ` Ian Stirling [this message]
2004-04-22 16:18   ` Meelis Roos
2004-04-22 18:08   ` Kim Holviala
2004-04-22 15:53 ` Tomasz Torcz
2004-04-22 18:10   ` Kim Holviala

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=40884165.5030407@mauve.plus.com \
    --to=ian.stirling@mauve.plus.com \
    --cc=kim@holviala.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=vonbrand@inf.utfsm.cl \
    /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