From: Segher Boessenkool <segher@chello.nl>
To: benh@kernel.crashing.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"David N. Welton" <davidw@dedasys.com>,
linux-kernel@vger.kernel.org
Subject: Re: forth interpreter as kernel module
Date: Sun, 07 Apr 2002 22:50:47 +0200 [thread overview]
Message-ID: <3CB0B124.70423121@chello.nl> (raw)
In-Reply-To: <E16tHSB-00078F-00@the-village.bc.nu> <20020405181627.22453@mailhost.mipsys.com>
benh@kernel.crashing.org wrote:
> Yes, an OpenFirmware emulator would be interesting. It would allow to
> softboot OF PCI cards on non-OF machines, and would allow to implement
> properly resume from sleep on some desktop G4s that will power off the
> PCI bus during sleep (some cards need to be re-softbooted, like video
> ones, and in some case, you really want the vendor firmware to run).
I'm writing a full OF implementation for OpenBios. It will also be
able to run in user space, which might be a better solution for things
like softboot (and besides, it makes development a lot easier).
It is supposed to be fully portable across all architectures that
run Linux.
Check out module Paflof from OpenBios CVS.
http://www.freiburg.linux.de/OpenBIOS/
Nothing very mature yet, so don't get too excited now.
Cheers,
Segher
next prev parent reply other threads:[~2002-04-07 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 23:49 forth interpreter as kernel module David N. Welton
2002-04-04 23:59 ` M. Edward (Ed) Borasky
2002-04-05 0:19 ` Alan Cox
2002-04-05 2:51 ` Eric W. Biederman
2002-04-05 18:16 ` benh
2002-04-07 20:50 ` Segher Boessenkool [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-06 1:22 Forth " Rick A. Hohensee
2002-04-06 5:10 ` M. Edward Borasky
2002-04-07 10:05 forth " Rick A. Hohensee
2002-04-08 8:53 Forth " Rick A. Hohensee
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=3CB0B124.70423121@chello.nl \
--to=segher@chello.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=davidw@dedasys.com \
--cc=linux-kernel@vger.kernel.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.