From: Jaco Kroon <jaco@kroon.co.za>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Sebastian Piechocki <sebekpi@poczta.onet.pl>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: i8042 access timings
Date: Thu, 27 Jan 2005 19:33:51 +0200 [thread overview]
Message-ID: <41F925FF.6000006@kroon.co.za> (raw)
In-Reply-To: <20050127113158.GB2975@ucw.cz>
Vojtech Pavlik wrote:
> On Thu, Jan 27, 2005 at 12:12:23PM +0100, Sebastian Piechocki wrote:
>
>>Dnia czwartek, 27 stycznia 2005 11:25, Vojtech Pavlik napisał:
>>
>>>On Thu, Jan 27, 2005 at 08:23:07AM +0200, Jaco Kroon wrote:
>>>
>>>>Sebastian Piechocki wrote:
>>>>
>>>>>As I said I'm sending you mails from kernel masters:)
>>>>
>>>>Thanks.
>>>>
>>>>
>>>>>If you haven't such a problem, please send them your dmesg with
>>>>>i8042.debug and acpi=off.
>>>>
>>>>I made an alternative plan. I applied a custom patch that gives me
>>>>far less output and prevents scrolling and gets what I hope is what
>>>>is required.
>>>
>>>... could you just increase the timeout value to some insane amount?
>>>That should take care of the AUX_LOOP output getting back only after
>>>issuing the next command.
>>
>>Increasing the timeout doesn't help. I've increased timout ten times and
>>the result is the same.
>
>
> OK, in that case the BIOS i8042 emulation just interferes badly with the
> real i8042 and I doubt we can do much else than keep the BIOS from
> interfering.
>
And just how do we do that?
--
There are only 10 kinds of people in this world,
those that understand binary and those that don't.
http://www.kroon.co.za/
next prev parent reply other threads:[~2005-01-27 17:36 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 [this message]
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
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=41F925FF.6000006@kroon.co.za \
--to=jaco@kroon.co.za \
--cc=akpm@osdl.org \
--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