From: Segher Boessenkool <segher@kernel.crashing.org>
To: "i2a" <i2a@gmx.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: open firmware
Date: Fri, 14 Oct 2005 15:17:47 +0200 [thread overview]
Message-ID: <f308ce32868b18c6be30cf2a28d86ade@kernel.crashing.org> (raw)
In-Reply-To: <20051014115753.M37114@quicknet.nl>
> The linuxppc kernel uses the open firmware to access the ppc machine=20=
> infos, I
> want to be able to program to the open firmware to. Although there is=20=
> a lost of
> info inside the ppc kernel I still want to know the internals=20
> (definitions etc)
> of =93open firmware=94.
>
> Has someone documentation available? On inet I only found the UI=20
> description :(
See http://playground.sun.com/1275/
Segher
next prev parent reply other threads:[~2005-10-14 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 12:04 open firmware i2a
2005-10-14 13:17 ` Segher Boessenkool [this message]
2005-10-14 15:34 ` i2a
2005-10-14 15:54 ` Hollis Blanchard
2005-10-20 15:17 ` Sven Luther
2005-10-20 23:33 ` CHRP specifications Hollis Blanchard
2005-10-21 5:18 ` Sven Luther
2005-10-22 13:22 ` i2a
2005-10-24 19:15 ` Sven Luther
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=f308ce32868b18c6be30cf2a28d86ade@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=i2a@gmx.net \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).