From: Sylvain Ferrand <sylvain.ferrand@polytechnique.edu>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Longhaul support for Via C3 (samuel 2) CPU and Via prosavage PM133 northbridge
Date: Mon, 17 Sep 2007 09:39:10 +0200 [thread overview]
Message-ID: <46EE2F1E.5000900@polytechnique.edu> (raw)
In-Reply-To: <46ED7FB1.60000@interia.pl>
Hi,
Sure, I'm interested for testing it! What can I do?
Regards
Sylvain
Rafał Bilski a écrit :
>> [...]
>> longhaul: VIA C3 'Samuel 2' [C5B] CPU detected. Longhaul v1 supported.
>> longhaul: No ACPI support. Unsupported northbridge
>>
>>
>> Does it mean that this motherboard is not supported, or I missed
>> something?
> Northbridge has AGP/PCI arbiter disable bits, but support for this
> northbridge was never tested. Let me know if You are interested in
> testing it.
prev parent reply other threads:[~2007-09-17 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 14:34 Longhaul support for Via C3 (samuel 2) CPU and Via prosavage PM133 northbridge sylvain
2007-09-16 19:10 ` Rafał Bilski
2007-09-17 7:39 ` Sylvain Ferrand [this message]
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=46EE2F1E.5000900@polytechnique.edu \
--to=sylvain.ferrand@polytechnique.edu \
--cc=cpufreq@lists.linux.org.uk \
--cc=rafalbilski@interia.pl \
/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