From: <benh@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"David N. Welton" <davidw@dedasys.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: forth interpreter as kernel module
Date: Fri, 5 Apr 2002 20:16:27 +0200 [thread overview]
Message-ID: <20020405181627.22453@mailhost.mipsys.com> (raw)
In-Reply-To: <E16tHSB-00078F-00@the-village.bc.nu>
>> I would be interested in comments on what should be fixed in the code,
>> although I may not have time to act on them.
>
>Strange. The one area forth does have sort of relevance may be outside the
>x86 world. The portable boot rom standards (the one everyone ignored for
>x86) is all about forth stuff. I don't know if anyone has use for a forth
>engine that can speak that ?
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).
Ben.
next prev parent reply other threads:[~2002-04-05 18:16 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 [this message]
2002-04-07 20:50 ` Segher Boessenkool
-- 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=20020405181627.22453@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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.