[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14425.1159496284@kao2.melbourne.sgi.com>
Date: Fri, 29 Sep 2006 12:18:04 +1000
From: Keith Owens <kaos@....com>
To: Bjorn Helgaas <bjorn.helgaas@...com>
cc: linux-kernel@...r.kernel.org, linux-ia64@...r.kernel.org
Subject: Re: KDB blindly reads keyboard port
Bjorn Helgaas (on Wed, 27 Sep 2006 16:11:00 -0600) wrote:
>On Tuesday 26 September 2006 20:45, Keith Owens wrote:
>> No support for legacy I/O ports could be a bigger problem than just
>> KDB.
>
>On Itanium (and I suppose on x86), ACPI theoretically tells us enough
>that we don't need to assume any legacy resources. Of course, Linux
>doesn't listen to everything ACPI is trying to tell it. But that's
>a Linux deficiency we should remedy.
>
>> To fix just KDB, apply this patch over kdb-v4.4-2.6.18-common-1 and
>> add 'kdb_skip_keyboard' to the boot command line on the offending
>> hardware.
>
>This doesn't feel like the right solution. Since firmware tells us
>whether the device is present, I think we should rely on that. If
>you want to use the device before ACPI is initialized, *then* you
>should pass a "kdb_use_keyboard" sort of flag.
I have never been a big fan of ACPI, having seen too many broken ACPI
tables. But if that is what you want ...
Bjorn, could you apply my previous patch anyway, boot your problem
system with kdb_skip_keyboard, drop into KDB and
'md4c1 acpi_kbd_controller_present'. That will quickly confirm if acpi
is detecting the absence of the keyboard on your system.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists