Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261937AbVAYNtT (ORCPT ); Tue, 25 Jan 2005 08:49:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261938AbVAYNtT (ORCPT ); Tue, 25 Jan 2005 08:49:19 -0500 Received: from [81.2.110.250] ([81.2.110.250]:55707 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S261937AbVAYNtQ (ORCPT ); Tue, 25 Jan 2005 08:49:16 -0500 Subject: Re: i8042 access timings From: Alan Cox To: Dmitry Torokhov Cc: linux-input@atrey.karlin.mff.cuni.cz, Linux Kernel Mailing List , Vojtech Pavlik In-Reply-To: <200501250241.14695.dtor_core@ameritech.net> References: <200501250241.14695.dtor_core@ameritech.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1106656268.14787.5.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 25 Jan 2005 12:44:08 +0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 736 Lines: 17 On Maw, 2005-01-25 at 07:41, Dmitry Torokhov wrote: > in i8042. It made me curious as we only wait between accesses to status > register but not data register. I peeked into FreeBSD code and they use > delays to access both registers and I wonder if that's the piece that > makes i8042 mysteriously fail on some boards. Maybe - my own experience is that the last boards I've seen that actually require the delays are the Digital Hinote laptops, so its only stuff only as far as I can tell - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/