public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ookhoi <ookhoi@dds.nl>
To: Daniel Quinlan <quinlan@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: setting cpu speed on crusoe
Date: Wed, 14 Feb 2001 15:31:19 +0100	[thread overview]
Message-ID: <20010214153119.K30236@ookhoi.dds.nl> (raw)
In-Reply-To: <20010210224855.D7877@bug.ucw.cz> <Pine.LNX.4.10.10102130928490.29787-100000@penguin.transmeta.com> <6y66idbiai.fsf@magnesium.transmeta.com>
In-Reply-To: <6y66idbiai.fsf@magnesium.transmeta.com>; from quinlan@transmeta.com on Wed, Feb 14, 2001 at 03:44:37AM -0800

Hi Daniel,

> > We're going through our docs and we have internal programs that
> > we'll release for this so that you'll not just have docs but
> > actually working code too. It just needs to be cleaned up a bit, and
> > go through the proper channels (ever wonder why open source gets
> > deveoped faster?). It really should be "any day now".
> 
> Working code is better anyway (and in this case, it's first).  Go to
> your favorite kernel.org mirror and check out
> 
>   /pub/linux/utils/cpu/crusoe/longrun-0.9.tar.gz
> 
> It does everything you could ever want and more, as long as you
> include the CPUID and MSR devices in your kernel, set up the devices
> correctly, etc.

Very cool. :-)  Will we also be able to do a software upgrade of the cpu
code morphing software in the future?

	Ookhoi

  reply	other threads:[~2001-02-14 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-03 22:39 setting cpu speed on crusoe Andrew Tridgell
2001-02-10 21:48 ` Pavel Machek
2001-02-13 17:33   ` Linus Torvalds
2001-02-14 11:44     ` Daniel Quinlan
2001-02-14 14:31       ` Ookhoi [this message]
2001-03-19 12:49       ` is it possible to upgrade crusoe code morphing software with linux? Ookhoi

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=20010214153119.K30236@ookhoi.dds.nl \
    --to=ookhoi@dds.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quinlan@transmeta.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