Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261170AbVA0UaG (ORCPT ); Thu, 27 Jan 2005 15:30:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261174AbVA0UaF (ORCPT ); Thu, 27 Jan 2005 15:30:05 -0500 Received: from pastinakel.tue.nl ([131.155.2.7]:40971 "EHLO pastinakel.tue.nl") by vger.kernel.org with ESMTP id S261170AbVA0U3x (ORCPT ); Thu, 27 Jan 2005 15:29:53 -0500 Date: Thu, 27 Jan 2005 21:29:47 +0100 From: Andries Brouwer To: Linus Torvalds Cc: Jaco Kroon , sebekpi@poczta.onet.pl, Vojtech Pavlik , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: i8042 access timings Message-ID: <20050127202947.GD6010@pclin040.win.tue.nl> References: <200501260040.46288.sebekpi@poczta.onet.pl> <41F888CB.8090601@kroon.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i X-Spam-DCC: MessageCare: pastinakel.tue.nl 1108; Body=1 Fuz1=1 Fuz2=1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 846 Lines: 20 On Thu, Jan 27, 2005 at 10:09:24AM -0800, Linus Torvalds 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. > The IO delay should be _before_ the read of the status, not after it. Andries - 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/