linux-kernel - Re: [PATCH 1/2] CPUFREQ: Enable acpi-cpufreq driver for VIA/Centaur CPUs

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 9 Jun 2009 11:45:19 -0500
From:	"Michael S. Zick" <lkml@...ethan.org>
To:	Chuck Ebbert <cebbert@...hat.com>
Cc:	Harald Welte <HaraldWelte@...tech.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Duane Griffin <duaneg@...da.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: [PATCH 1/2] CPUFREQ: Enable acpi-cpufreq driver for VIA/Centaur CPUs

On Tue June 9 2009, Chuck Ebbert wrote:
> On Tue, 9 Jun 2009 07:26:11 -0500
> "Michael S. Zick" <lkml@...ethan.org> wrote:
> 
> > > Sounds fine with me. But what I would definitely suggest merging before 2.6.30
> > > is the marking e_powersaver EXPERIMENTAL + DANGEROUS patch.
> > >  
> > 
> > As posted somewhere in this thread,
> > the acpi-cpufreq controller appears to work on my machine in initial tests.
> 
> It works great on the Samsung NC20 with an x86_64 kernel.
>

For non-NetBook aware readers, that means the:
VIA Nano U2250 processor with the VX800 system chipset.

Mike

> --
> 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/
> 
> 


--
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/