From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Nocera Subject: Re: [git pull] Input updates for 2.6.34-rc6 Date: Thu, 13 May 2010 15:47:31 +0100 Message-ID: <1273762051.2308.4671.camel@localhost.localdomain> References: <20100513075728.GF30110@core.coreip.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from relay1-d.mail.gandi.net ([217.70.183.193]:42747 "EHLO relay1-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755763Ab0EMOrm (ORCPT ); Thu, 13 May 2010 10:47:42 -0400 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Linus Torvalds Cc: Dmitry Torokhov , Andrew Morton , Linux Kernel Mailing List , linux-input@vger.kernel.org On Thu, 2010-05-13 at 07:35 -0700, Linus Torvalds wrote: > > On Thu, 13 May 2010, Dmitry Torokhov wrote: > > > > Bastien Nocera (1): > > Input: i8042 - do not try to probe ports on Intel Apple Macs > > I pulled, but I skipped the last commit, because I think this one is > fundamentally _wrong_. > > It is _not_ maintainable to create random tables of exceptions ("DMI > tables"), and it's actively _wrong_ to do for something like this where we > not only have historically worked perfectly well, and this apparently > tries to hide some other bug (the commit says "could potentially lock > up/hang/wait for timeout for long periods of time"). > So if somebody saw "could potentially lock up/hang/wait" issues, then > dangit, say what those issues are, AND LET'S FIX THEM! And not like this, > trying to hide them for some particular machines, rather than fixing the > actual underlying detection bug. I'm waiting for your debug instructions on that one, because we already looked at that with Dmitry. I already got that patch in my distribution, and now my machine boots up uninterrupted. The lock is somewhat random, and will go away as soon as I press the power button on my machine. Maybe you didn't update to the latest firmwares on you Mac Mini, and didn't see the problem with the updated BIOSes, I don't know.