From: Dave Jones <davej@redhat.com>
To: Vincent Stehl? <vincent.stehle@free.fr>
Cc: cpufreq@www.linux.org.uk
Subject: Re: longhaul: Unknown VIA CPU
Date: Wed, 3 Sep 2003 01:49:57 +0100 [thread overview]
Message-ID: <20030903004949.GA7278@redhat.com> (raw)
In-Reply-To: <3F55187F.70707@free.fr>
On Wed, Sep 03, 2003 at 12:23:59AM +0200, Vincent Stehl? wrote:
> 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.
Nehemiah is still unsupported as I've not seen a production one thats
actually capable of working properly yet. Still waiting to hear back
from the folks at Centaur.
Dave
--
Dave Jones http://www.codemonkey.org.uk
next prev parent reply other threads:[~2003-09-03 0: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 [this message]
2003-09-03 13:49 ` Sven Dowideit
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=20030903004949.GA7278@redhat.com \
--to=davej@redhat.com \
--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