From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Paul Ionescu <i_p_a_u_l@yahoo.com>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [RFC] cpufreqtools
Date: Tue, 26 Oct 2004 21:57:12 +0200 [thread overview]
Message-ID: <20041026195712.GA678@dominikbrodowski.de> (raw)
In-Reply-To: <pan.2004.10.25.10.07.03.511563@yahoo.com>
On Mon, Oct 25, 2004 at 01:07:05PM +0300, Paul Ionescu wrote:
> Hi Jeremy,
>
> I think too that dbus is the way to go.
> If there is not any big issue with dbus, we should use it for uniformity.
> Why invent a new protocol for this if not really necessary ?
> Consistent UI/policy tools is a nice thing to have.
I'd like to keep a "low-overhead" support by the C calls to libcpufreq,
especially for the embedded area [I'm thinking especially of Johan
Pouwelse's work]. A daemon, which may both accept a socket or dbus input,
depending on configuration, can then be added on top of it. And as such I'd
prefer to get a first revision of the cpufreqtools out soon, and add the
daemon and dbus support later on. Patches will be _very_ welcome then.
Thanks,
Dominik
next prev parent reply other threads:[~2004-10-26 19:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 17:22 [RFC] cpufreqtools Dominik Brodowski
2004-10-21 18:51 ` Dave Jones
2004-10-22 14:39 ` Bruno Ducrot
2004-10-22 14:57 ` Dominik Brodowski
2004-10-22 17:21 ` Bruno Ducrot
2004-10-22 17:47 ` Dominik Brodowski
2004-10-22 18:19 ` Bruno Ducrot
2004-10-24 16:30 ` Jeremy Fitzhardinge
2004-10-25 10:07 ` Paul Ionescu
2004-10-26 19:57 ` Dominik Brodowski [this message]
2004-10-25 9:01 ` Mattia Dongili
2004-10-25 11:11 ` Dominik Brodowski
2004-10-25 12:17 ` Mattia Dongili
2004-10-25 12:42 ` Dominik Brodowski
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=20041026195712.GA678@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=cpufreq@www.linux.org.uk \
--cc=i_p_a_u_l@yahoo.com \
/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