From: Jeff Garzik <jgarzik@pobox.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Daniel Egger <degger@fhm.edu>,
Dave Jones <davej@codemonkey.org.uk>,
Joseph <jospehchan@yahoo.com.tw>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why does C3 CPU downgrade in kernel 2.4.20?
Date: Wed, 11 Dec 2002 14:42:44 -0500 [thread overview]
Message-ID: <20021211194244.GA9554@gtf.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1021211134909.19397B-100000@gatekeeper.tmr.com>
On Wed, Dec 11, 2002 at 01:51:13PM -0500, 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).
We don't know for sure; however the cnn.com story on these PCs had a
"Via C3" logo in the story's graphic, so it's strongly probable :)
next prev parent reply other threads:[~2002-12-11 19:35 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 [this message]
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
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=20021211194244.GA9554@gtf.org \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=davidsen@tmr.com \
--cc=degger@fhm.edu \
--cc=jospehchan@yahoo.com.tw \
--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.