From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Jaco Kroon <jaco@kroon.co.za>, Andries Brouwer <aebr@win.tue.nl>,
Linus Torvalds <torvalds@osdl.org>,
sebekpi@poczta.onet.pl, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: i8042 access timings
Date: Sat, 29 Jan 2005 12:02:13 -0800 [thread overview]
Message-ID: <41FBEBC5.8020404@osdl.org> (raw)
In-Reply-To: <20050128183955.GA2640@ucw.cz>
Vojtech Pavlik wrote:
> On Fri, Jan 28, 2005 at 04:20:58PM +0200, Jaco Kroon wrote:
>
>>Vojtech Pavlik wrote:
>>
>>>On Thu, Jan 27, 2005 at 09:29:47PM +0100, Andries Brouwer wrote:
>>>
>>>
>>>
>>>>>So what _might_ happen is that we write the command, and then
>>>>>i8042_wait_write() thinks that there is space to write the data
>>>>>immediately, and writes the data, but now the data got lost because the
>>>>>buffer was busy.
>>>>
>>>>Hmm - I just answered the same post and concluded that I didnt understand,
>>>>so you have progressed further. I considered the same possibility,
>>>>but the data was not lost since we read it again later.
>>>>Only the ready flag was lost.
>>>
>>>
>>>What I believe is happening is that we're talking to SMM emulation of
>>>the i8042, which doesn't have a clue about these commands, while the
>>>underlying real hardware implementation does. And because of that they
>>>disagree on what should happen when the command is issued, and since the
>>>SMM emulation lazily synchronizes with the real HW, we only get the data
>>>back with the next command.
>>>
>>>I still don't have an explanation why both 'usb-handoff' and 'acpi=off'
>>>help, I'd expect only the first to, but it might be related to the SCI
>>>interrupt routing which isn't done when 'acpi=off'. Just a wild guess.
>>>
>>
>>Ok, I'm not too clued up with recent hardware and the BIOS programming
>>that goes with it (being a system admin/application programmer), what
>>exactly is usb-handoff?
>
>
> usb-handoff is a kernel option that enables a PCI quirk routine that
> takes the USB controller out of BIOS's hands. Until that is done (the
> linux USB drivers also do it, only later), the BIOS owns the USB
> controller and tries to emulate a PS/2 mouse and keyboard for systems
> which can't handle USB.
>
>
>> acpi=off obviously just turns all acpi support
>>in the kernel off.
>
>
> Indeed.
>
>
>>SCI is also a new abbreviation I haven't seen
>>before.
>
>
> System Configuration Interrupt. In addition to SMI (System Management
> Interrupt), these are two interrupts the BIOS uses to do its job behind
> the operating system's back.
ACPI 2.0 spec says:
System Control Interrupt (SCI)
A system interrupt used by hardware to notify the OS of ACPI events.
The SCI is an active, low, shareable, level interrupt.
--
~Randy
next prev parent reply other threads:[~2005-01-29 20:11 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501260040.46288.sebekpi@poczta.onet.pl>
2005-01-27 6:23 ` i8042 access timings Jaco Kroon
2005-01-27 10:25 ` Vojtech Pavlik
2005-01-27 11:12 ` Sebastian Piechocki
2005-01-27 11:31 ` Vojtech Pavlik
2005-01-27 17:33 ` Jaco Kroon
2005-01-27 18:09 ` Linus Torvalds
2005-01-27 20:29 ` Andries Brouwer
2005-01-27 20:41 ` Dmitry Torokhov
2005-01-27 23:11 ` Andries Brouwer
2005-01-28 13:17 ` Vojtech Pavlik
2005-01-28 14:20 ` Jaco Kroon
2005-01-28 18:39 ` Vojtech Pavlik
2005-01-29 19:59 ` Jaco Kroon
2005-01-29 23:21 ` Dmitry Torokhov
2005-01-29 20:02 ` Randy.Dunlap [this message]
2005-01-27 20:51 ` Jaco Kroon
2005-01-27 21:17 ` Linus Torvalds
2005-01-27 22:12 ` Jaco Kroon
2005-01-27 22:36 ` Linus Torvalds
2005-01-27 23:40 ` Dmitry Torokhov
2005-01-28 5:52 ` Jaco Kroon
2005-02-04 19:54 ` Bukie Mabayoje
2005-01-28 11:04 ` Vojtech Pavlik
2005-01-27 20:23 ` Andries Brouwer
2005-01-25 7:41 Dmitry Torokhov
2005-01-25 10:51 ` Andries Brouwer
2005-01-25 19:17 ` Dmitry Torokhov
2005-01-25 19:25 ` Vojtech Pavlik
2005-01-25 19:41 ` Dmitry Torokhov
2005-01-25 19:46 ` Andries Brouwer
2005-01-25 20:37 ` Lee Revell
2005-01-27 15:14 ` Alan Cox
2005-01-27 16:24 ` Vojtech Pavlik
2005-01-27 16:34 ` Bill Rugolsky Jr.
2005-01-27 16:37 ` Vojtech Pavlik
2005-02-13 0:16 ` Bill Rugolsky Jr.
2005-02-13 8:22 ` Vojtech Pavlik
2005-02-13 16:17 ` Bill Rugolsky Jr.
2005-01-27 17:45 ` Andries Brouwer
2005-01-28 14:55 ` Vojtech Pavlik
2005-01-25 12:44 ` Alan Cox
2005-01-25 12:44 ` Alan Cox
2005-01-26 15:43 ` Vojtech Pavlik
2005-01-26 16:36 ` Dmitry Torokhov
2005-01-26 17:05 ` linux-os
2005-01-26 18:30 ` Dmitry Torokhov
2005-01-27 10:19 ` 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=41FBEBC5.8020404@osdl.org \
--to=rddunlap@osdl.org \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--cc=jaco@kroon.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=sebekpi@poczta.onet.pl \
--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