linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Mats Johannesson <spamcan@abcbredband.net>
Cc: pavel@suse.cz, legolas558@users.sourceforge.net,
	dmitry.torokhov@gmail.com, astarikovskiy@suse.de,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: Laptop keyboard unusable when ACPI is active
Date: Fri, 23 Nov 2007 23:04:56 -0500	[thread overview]
Message-ID: <200711232304.57652.lenb@kernel.org> (raw)
In-Reply-To: <20071123084443.2cf6b61e@loke.fish.not>

On Friday 23 November 2007 02:44, Mats Johannesson wrote:

> The bad interaction between ACPI controlled EC (embedded controller)
> and the i8042 interrupt handler is theorized about in detail at OLPCs
> http://dev.laptop.org/ticket/2401 - almost at the end of that page.
> Thanks to Daniele C for the link.

huh?

I believe that the OLPC XO1 does not run in ACPI mode
and thus does not use the ACPI EC driver to talk to
the EC on their board.

Presumably they use some native embedded controller driver to
talk to their platform specific embedded controller.

I don't know why they call their interrupt an SCI.
Per above, it can't be an ACPI SCI.  Presumably they
call it that b/c their chipset documentation calls it
that too, on the (invalid) assumption that an ACPI-enabled
OS and firmware would be running on the hardware.

Please let me know if I'm wrong.

-Len

      reply	other threads:[~2007-11-24  4:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23  7:44 Laptop keyboard unusable when ACPI is active Mats Johannesson
2007-11-24  4:04 ` Len Brown [this message]

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=200711232304.57652.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=astarikovskiy@suse.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=legolas558@users.sourceforge.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=spamcan@abcbredband.net \
    /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).