linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Bastien Nocera <hadess@hadess.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	pjones@redhat.com, vojtech@suse.cz
Subject: Re: [PATCH] Disable i8042 checks on Intel Apple Macs
Date: Fri, 22 Jan 2010 14:49:36 -0800	[thread overview]
Message-ID: <4B5A2B80.8040904@zytor.com> (raw)
In-Reply-To: <51f3faa71001221433k72f20addg48e0735fe1b032d@mail.gmail.com>

On 01/22/2010 02:33 PM, Robert Hancock wrote:
>>
>> You think it's reasonable to have the keyboard not work because
>> someone's KVM switch was in the wrong position when the system booted?
>> Sorry, that's not how the world works.  It's sad that someone had the
>> bright idea that things should work that way, but that is definitely a
>> regression I wouldn't want to deal with.
> 
> I don't imagine most KVM switches would result in this - they usually
> emulate the presence of a keyboard and mouse on all ports even if the
> input isn't the active one. It could be the reporter had an older
> switch that didn't do this.
> 

The good ones do.  The bad (cheap) ones just provide for a basic
electric disconnect.  Heck, there used to be mechanical KVMs...

> I expect that it's quite common for the BIOS to disable the controller
> if no device is detected, though. I think the idea is to prevent a
> useless device from showing up in Device Manager and free up resources
> for other devices. Problem is if it does this, we don't really know
> what it did other than remove the PNP entry, and whether using the
> controller anyway will work safely.
> 
> In any case, it's unlikely (though I admit I'm uncertain) that Windows
> is going to blindly probe for an 8042 controller if the PNP
> information doesn't indicate that one should be there - at least not
> if it's using the ACPI HAL. And for this sort of hardware
> compatibility issue, doing things differently than Windows does is
> ultimately asking for trouble in the long term. It's highly
> unreasonable to break that just for an unlikely corner case.

It's not unlikely - it's reality.  Furthermore, BIOS programmers do
weird things all the time, especially to support, say, old Windows
versions that noone cares about anymore but mattered then.

	-hpa

  reply	other threads:[~2010-01-22 22:50 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 18:23 [PATCH] Disable i8042 checks on Intel Apple Macs Bastien Nocera
2010-01-20 19:14 ` Justin P. Mattock
2010-01-20 19:37   ` Bastien Nocera
2010-01-20 19:54     ` Justin P. Mattock
2010-01-21  0:41 ` Robert Hancock
2010-01-21  1:31   ` Bastien Nocera
2010-01-21  2:19     ` Robert Hancock
2010-01-21 18:55   ` Dmitry Torokhov
2010-01-21 21:39     ` Robert Hancock
2010-01-21 21:42       ` Bastien Nocera
2010-01-21 21:49       ` Justin P. Mattock
2010-01-22  0:29         ` Robert Hancock
2010-01-22  1:20           ` Justin P. Mattock
2010-01-22  2:09             ` Bastien Nocera
2010-01-22  2:30               ` Robert Hancock
2010-01-22  2:53                 ` Bastien Nocera
2010-01-22  2:31               ` Justin P. Mattock
2010-01-21 22:17       ` Dmitry Torokhov
2010-01-22  0:26         ` Robert Hancock
2010-01-22 17:46           ` H. Peter Anvin
2010-01-22 18:15             ` Bastien Nocera
2010-01-22 22:33             ` Robert Hancock
2010-01-22 22:49               ` H. Peter Anvin [this message]
2010-01-25 16:34         ` Vojtech Pavlik
2010-01-25 21:32           ` H. Peter Anvin
2010-01-25 22:15             ` Dmitry Torokhov
2010-01-25 22:18               ` H. Peter Anvin
2010-01-25 22:30                 ` Dmitry Torokhov
2010-01-25 23:05                   ` H. Peter Anvin
2010-01-25 23:28                     ` Dmitry Torokhov
2010-01-25 23:31                       ` H. Peter Anvin
2010-05-04 17:06               ` Bastien Nocera
2010-05-04 17:23                 ` Dmitry Torokhov
2010-05-04 17:37                   ` Bastien Nocera
  -- strict thread matches above, loose matches on Subject: below --
2010-05-04 17:36 Bastien Nocera
2010-05-04 17:55 ` Pekka Enberg
2010-05-04 18:02 ` Dmitry Torokhov
2010-05-05  9:18   ` Bastien Nocera
2010-05-05 21:27 ` Kyle McMartin
2010-05-12  0:11 Bastien Nocera
2010-05-12 10:51 ` Felipe Contreras
2010-05-12 11:00   ` Felipe Contreras
2010-05-12 17:51   ` Dmitry Torokhov

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=4B5A2B80.8040904@zytor.com \
    --to=hpa@zytor.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hadess@hadess.net \
    --cc=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pjones@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).