From: P@draigBrady.com
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why does C3 CPU downgrade in kernel 2.4.20?
Date: Thu, 12 Dec 2002 10:19:05 +0000 [thread overview]
Message-ID: <3DF86299.3080309@draigBrady.com> (raw)
In-Reply-To: <1039640441.18412.24.camel@irongate.swansea.linux.org.uk>
Alan Cox wrote:
> On Wed, 2002-12-11 at 18:51, Bill Davidsen wrote:
>
>>Is this the CPU in the $200 "Lindows" PC Wal-Mart is selling? I was
>>thinking of one for a low volume router, and it looks as if there are two
>>VIA chips called C3 (or advertizers have hacked the specs).
>
> It is. Its a nice CPU for appliances. FPU is nondescript, integer
> performance is sort of the same as an equivalently clocked celewrong for
> the current Ezra core at least. The older Samuel II core seems a little
> slower.
>
> There is also a subspecies that comes in at 500-600MHz and is designed
> for low power fanless operation (though with a decent sized heatsink the
> same is true for the 1GHz ones).
Although don't try to do this in 1U with 1GHz chips unless you clock
down and reduce the voltage (you need a "fair amount" of free space
above the heatsink to dissipate the heat). Hmm that reminds me I must
complete the auto voltage selection code in cpufreq.
> If you think the Walmart PC is cool take a look at the EPIA board or see
> www.mini-itx.com. 60W for a complete PC
I built a "no moving parts" router thingy in 1U that used max 19W.
You get a nice MTBF (5.25 years for our config) when there's nothing
mechanical as well as a good power saving. The main parts were:
PSU: EOS VLT60-3000 (now celetron)
MB: Advantech PCM9576
CPU: Ezra C3 866a
HD: 64MB compact flash
Pádraig.
next prev parent reply other threads:[~2002-12-12 10:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 4:02 Why does C3 CPU downgrade in kernel 2.4.20? Joseph
2002-12-10 5:52 ` Dave Jones
2002-12-10 7:22 ` Daniel Egger
2002-12-10 7:24 ` Dave Jones
2002-12-10 7:53 ` Daniel Egger
2002-12-10 12:40 ` Juan Quintela
2002-12-10 15:40 ` Daniel Egger
2002-12-10 16:51 ` Alan Cox
2002-12-10 19:39 ` Daniel Egger
2002-12-10 20:17 ` Jeff Garzik
2002-12-10 21:24 ` Alan Cox
2002-12-11 18:51 ` Bill Davidsen
2002-12-11 19:14 ` Dave Jones
2002-12-11 19:42 ` Jeff Garzik
2002-12-11 19:51 ` Joel Jaeggli
2002-12-12 9:17 ` Joseph
2002-12-12 13:33 ` Dave Jones
2002-12-13 6:55 ` Joseph
2002-12-13 11:04 ` Daniel Egger
2002-12-13 11:57 ` Dave Jones
2002-12-11 21:00 ` Alan Cox
2002-12-12 10:19 ` P [this message]
2002-12-11 13:19 ` Denis Vlasenko
2002-12-11 10:58 ` Dave Jones
2002-12-11 19:09 ` Denis Vlasenko
2002-12-11 14:59 ` Dave Jones
2002-12-12 18:09 ` Pavel Machek
2002-12-14 16:46 ` Denis Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DF86299.3080309@draigBrady.com \
--to=p@draigbrady.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.