From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Jorgen <jorgen@greven.dk>, Dave Jones <davej@codemonkey.org.uk>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Enhanced PowerSaver driver
Date: Wed, 31 Jan 2007 23:13:58 +0100 [thread overview]
Message-ID: <45C114A6.4040801@interia.pl> (raw)
In-Reply-To: <loom.20070131T122840-94@post.gmane.org>
[...]
>
> I have a board (IB798) with a Via Eden CPU (a C7 deviate). On kernel 2.6.16.38 I
> tried to compile and load Via's longhaul driver. When I started cpufreq, the O/S
> crashed.
>
This is rather bad sign. Looks like I spoke to soon.
> If e.g. Rafa³ create som patches for the original longhaul driver, from ideas
> based on Via's code, I will install them, test and give feedback.
>
Thanks.
After looking into code I have found two things:
- it is using "disable bus master bit on each PCI device"... for C7?!,
- it is using current CPU f and vcc to find table for it. I don't like
this idea. If CPU has min/max info why not use it? Strange thing in C7
is that it is starting at lowest supported frequency. BIOS has to switch it
to max. As You can read at viaarena, BIOS is only doing it when "optimized
defaults" are loaded. Looks like it isn't default. What will happen if
driver will search table for CPU running at lowest frequency? Probably
processors with different max can have same min frequency.
Dave: Can I repost e_powersaver with "experimental" and some small
changes? Sorry.
> Brgds Jorgen
Regards
Rafa³
----------------------------------------------------------------------
Fergie i jej biodra.... - zobacz >> http://link.interia.pl/f19ed
next prev parent reply other threads:[~2007-01-31 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 13:01 Enhanced PowerSaver driver Rafał Bilski
2007-01-28 14:25 ` Dave Jones
2007-01-28 16:53 ` Rafał Bilski
2007-01-31 11:33 ` Jorgen
2007-01-31 22:13 ` Rafał Bilski [this message]
2007-01-31 22:45 ` Dave Jones
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=45C114A6.4040801@interia.pl \
--to=rafalbilski@interia.pl \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=jorgen@greven.dk \
/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.