From: Sven Dowideit <svenud@ozemail.com.au>
To: "Vincent Stehlé" <vincent.stehle@free.fr>
Cc: cpufreq@www.linux.org.uk
Subject: Re: longhaul: Unknown VIA CPU
Date: Wed, 03 Sep 2003 23:49:55 +1000 [thread overview]
Message-ID: <1062596994.574.1.camel@sven> (raw)
In-Reply-To: <3F55187F.70707@free.fr>
I sent DaveJones a patch that at least says that the Nehemiah is not
implemented, but i have not heard from him since.. also, the email
address will need to be changed to the codemonkey one :)
However, VIA have not yet made that info available to the public (I'm
hoping Dave has a copy)
sven
On Wed, 2003-09-03 at 08:23, Vincent Stehlé wrote:
> Hi,
>
> I tried to get the longhaul module to work on my VIA EPIA M10000
> motherboard (C3-2 cpu), but I did not succeed yet.
>
> I use cpufreq 2.4.21-2, and I see the following message in the syslog
> when I "modprobe longhaul":
>
> longhaul: Unknown VIA CPU. Contact davej@suse.de
>
> I'd be pleased to help with what seems to be a "new" cpu, but I do not
> know what to begin with.
>
> Here is my /proc/cpuinfo; don't know if this is of any use to anyone (:
>
> ---
> processor : 0
> vendor_id : CentaurHauls
> cpu family : 6
> model : 9
> model name : VIA Nehemiah
> stepping : 1
> cpu MHz : 999.531
> cache size : 64 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu de tsc msr mtrr pge cmov mmx fxsr sse
> bogomips : 1992.29
> ---
>
> Regards,
next prev parent reply other threads:[~2003-09-03 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 22:23 longhaul: Unknown VIA CPU Vincent Stehlé
2003-09-03 0:49 ` Dave Jones
2003-09-03 13:49 ` Sven Dowideit [this message]
2003-09-03 12:00 ` Dave Jones
2003-09-03 12:52 ` Ducrot Bruno
2003-09-03 13:24 ` Dave Jones
2003-09-03 13:45 ` Ducrot Bruno
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=1062596994.574.1.camel@sven \
--to=svenud@ozemail.com.au \
--cc=cpufreq@www.linux.org.uk \
--cc=vincent.stehle@free.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox