linux-kernel - Re: Lenovo 3000 N100 i8042 problems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080903213258.GC14620@khazad-dum.debian.net>
Date:	Wed, 3 Sep 2008 18:32:58 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Jiri Kosina <jkosina@...e.cz>,
	Daniel Barkalow <barkalow@...ervon.org>,
	linux-kernel@...r.kernel.org,
	Christopher Desjardins <cddesjardins@...il.com>
Subject: Re: Lenovo 3000 N100 i8042 problems

On Wed, 03 Sep 2008, Dmitry Torokhov wrote:
> On Wed, Sep 03, 2008 at 01:50:35PM +0200, Jiri Kosina wrote:
> > On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> > > I guess we could use System's product name to differentiate between 
> > > Cristopher's and Daniel's boards. Although I must admit it is the very 
> > > first time when I see a box that behaves better with active mux. DOes 
> > > Vista use active mux nowadays? Because if it is not then I bet there is 
> > > (or shortly will be) a BIOS update fixing legacy mode on Daniel's box.
> > 
> > I guess so, yes.
> > 
> > On the other hand, this might also be viewed as regression (we made 
> > Daniel's hardware behave worse with recent kernel than it did before), so 
> > I think we still would like to have this fixed. What about the patch 
> > below, adding the match on System's product name, as you suggested? 
> > Thanks.
> > 
> 
> I agree. Daniel, could you please try the patch to make sure it
> restores the previous behavior for you and I will push it through.

I fell I need to warn you guys that you are likely breaking machines that
match that DMI info but have a newer BIOS, unless they use different BIOSes
(not enough data without a full dmidecode output from the other machine).

But I really don't care either way, since this is not about ThinkPads :)

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/