From: "H. Peter Anvin" <hpa@zytor.com>
To: sparclinux@vger.kernel.org
Subject: Re: klibc and SPARC
Date: Wed, 17 May 2006 20:57:39 +0000 [thread overview]
Message-ID: <446B8E43.205@zytor.com> (raw)
In-Reply-To: <e4g1ho$dae$1@terminus.zytor.com>
[Resend to fix Cc: list]
Followup to: <20060517.134042.27108210.davem@davemloft.net>
By author: "David S. Miller" <davem@davemloft.net>
In newsgroup: linux.dev.sparclinux
>
> From: "H. Peter Anvin" <hpa@zytor.com>
> Date: Wed, 17 May 2006 13:37:12 -0700 (PDT)
>
> > Is there a way to get that information from userspace, and if not,
> > should there be a general way to do it or an ad hoc solution? It sort
> > of looks like arch/sparc64/prom describes a form of filesystem, but I
> > don't see any obvious userspace interface.
>
> There are two ways.
>
> First option is to mount the "openpromfs" filesystem under
> /proc/openprom, the full firmware device tree and properties are
> available under there as a filesystem.
Just found that ;)
> The second option is to load the /dev/openprom driver, which you open,
> and then access using ioctls() defined in <asm/openpromio.h>
Does it make sense to say that these prom configurations are only
recognized by kinit if openpromfs is available (without which it will
simply behave as on any other platform), or should I go through the
additional trouble of supporting both methods?
-hpa
next prev parent reply other threads:[~2006-05-17 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 20:37 klibc and SPARC H. Peter Anvin
2006-05-17 20:40 ` David S. Miller
2006-05-17 20:43 ` H. Peter Anvin
2006-05-17 20:57 ` H. Peter Anvin [this message]
2006-05-17 22:32 ` David S. Miller
2006-05-17 22:36 ` H. Peter Anvin
2006-05-17 22:41 ` David S. Miller
2006-05-17 23:10 ` H. Peter Anvin
2006-05-17 23:33 ` David S. Miller
2006-05-17 23:38 ` H. Peter Anvin
2006-05-18 19:17 ` H. Peter Anvin
2006-05-18 19:46 ` David S. Miller
2006-05-18 20:16 ` H. Peter Anvin
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=446B8E43.205@zytor.com \
--to=hpa@zytor.com \
--cc=sparclinux@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.