All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wayne Wylupski" <wayne@connact.com>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: userspace not supported for longrun?
Date: Tue, 1 Jun 2004 19:52:05 -0400	[thread overview]
Message-ID: <005701c44833$71e8ca30$6900a8c0@DEVELOPER> (raw)
In-Reply-To: 20040601093110.GE7926@poupinou.org

> It's by choice.  Even though there exist some algo. for which it's seems
> there are better choice over the longrun facilities in order to switch
> automatically the frequency of the processor, it's hard to get those
> algo. to mainline mostly due to some kind of patent issues
> apparently.  So for now the longrun driver do not have the facilities to
> make what you request.  Would be fine perhaps to add that, but I'm
> not sure it's in a high priority item for now.

Thank you.  The issue is that Fedora Core 2 ships with 'cpuspeed' as a
service, which fails on machines with Crusoe chips because it assumes
there's a userspace governor without first checking whether there it is
available.

Would it really violate patents if the userspace governor were allowed
to work along the existing policies ("powersave" and "performance")?  Or is
it that
the use of 'cpuspeed' might violate the patent?  Please help me understand
this,
because I'm going to try to recommend how FC2 should support Crusoe and
processors with longrun support.

If there's an existing e-mail, memo, or document which explains this, I
would be
read and work with it.  The existing documentation does not cover this.

Thanks,
Wayne Wylupsxki

  reply	other threads:[~2004-06-01 23:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01  3:40 userspace not supported for longrun? Wayne Wylupski
2004-06-01  9:31 ` Bruno Ducrot
2004-06-01 23:52   ` Wayne Wylupski [this message]
2004-06-02  9:30     ` Bruno Ducrot
2004-06-02 12:19     ` Dominik Brodowski
2004-06-02 13:28       ` Bruno Ducrot
2004-06-03  4:18         ` Wayne Wylupski
2004-06-02 15:39       ` Francesco Poli
2004-06-02 12:40 ` 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='005701c44833$71e8ca30$6900a8c0@DEVELOPER' \
    --to=wayne@connact.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ducrot@poupinou.org \
    /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.