Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261275AbVBMQRM (ORCPT ); Sun, 13 Feb 2005 11:17:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261276AbVBMQRM (ORCPT ); Sun, 13 Feb 2005 11:17:12 -0500 Received: from 209-166-240-202.cust.walrus.com ([209.166.240.202]:64462 "EHLO ti41.telemetry-investments.com") by vger.kernel.org with ESMTP id S261275AbVBMQRJ (ORCPT ); Sun, 13 Feb 2005 11:17:09 -0500 Date: Sun, 13 Feb 2005 11:17:09 -0500 From: "Bill Rugolsky Jr." To: Vojtech Pavlik Cc: Alan Cox , Lee Revell , Andries Brouwer , dtor_core@ameritech.net, linux-input@atrey.karlin.mff.cuni.cz, Linux Kernel Mailing List Subject: Re: i8042 access timings Message-ID: <20050213161709.GA22287@ti64.telemetry-investments.com> Mail-Followup-To: "Bill Rugolsky Jr." , Vojtech Pavlik , Alan Cox , Lee Revell , Andries Brouwer , dtor_core@ameritech.net, linux-input@atrey.karlin.mff.cuni.cz, Linux Kernel Mailing List References: <200501250241.14695.dtor_core@ameritech.net> <20050125105139.GA3494@pclin040.win.tue.nl> <20050125194647.GB3494@pclin040.win.tue.nl> <1106685456.10845.40.camel@krustophenia.net> <1106838875.14782.20.camel@localhost.localdomain> <20050127163431.GA31212@ti64.telemetry-investments.com> <20050127163714.GA15327@ucw.cz> <20050213001659.GA7349@ti64.telemetry-investments.com> <20050213082246.GC1535@ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050213082246.GC1535@ucw.cz> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 910 Lines: 23 On Sun, Feb 13, 2005 at 09:22:46AM +0100, Vojtech Pavlik wrote: > And I suppose it was running just fine without the patch as well? Correct. > The question was whether the patch helps, or whether it is not needed. If you look again at the patch I posted, it only borrowed a few lines of the patch from Dmitry that started this thread; I eliminated Alan's recent udelay(50) addition, reduced the loop delay, and added debug printks to the *_wait routines to determine whether the loop is ever taken. At least so far, those debugging statements have produced no output. I'll use the machine a bit and report back if I trigger anything. Regards, Bill Rugolsky - 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/