All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: sparclinux@vger.kernel.org
Subject: klibc and SPARC
Date: Wed, 17 May 2006 20:37:12 +0000	[thread overview]
Message-ID: <e4g1ho$dae$1@terminus.zytor.com> (raw)

Hello all,

As most of you know, I'm trying to move a bunch of Linux
initialization code into early userspace, "klibc".  This is now in
2.6.17-rc4-mm1, and I've gotten a sparc64-related bug report,
specifially related to the following:

[arch/sparc64/kernel/setup.c]


#ifdef CONFIG_IP_PNP
        if (!ic_set_manually) {
                int chosen = prom_finddevice ("/chosen");
                u32 cl, sv, gw;

                cl = prom_getintdefault (chosen, "client-ip", 0);
                sv = prom_getintdefault (chosen, "server-ip", 0);
                gw = prom_getintdefault (chosen, "gateway-ip", 0);
                if (cl && sv) {
                        ic_myaddr = cl;
                        ic_servaddr = sv;
                        if (gw)
                                ic_gateway = gw;
#if defined(CONFIG_IP_PNP_BOOTP) || defined(CONFIG_IP_PNP_RARP)
                        ic_proto_enabled = 0;
#endif
                }
        }
#endif

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.

	-hpa

             reply	other threads:[~2006-05-17 20:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 20:37 H. Peter Anvin [this message]
2006-05-17 20:40 ` klibc and SPARC David S. Miller
2006-05-17 20:43 ` H. Peter Anvin
2006-05-17 20:57 ` H. Peter Anvin
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='e4g1ho$dae$1@terminus.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.