All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Determining boot server and own IP on sparc64-ieee1275
Date: Wed, 06 Jul 2011 14:13:20 +0200	[thread overview]
Message-ID: <4E145160.2040203@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]

Hello, David. I'm currently working on improving network support in
GRUB2.  On IEEE1275 we use read/write functions to receive/send packets
in conjunction with a IP+UDP+ARP+BOOTP+TFTP implementation. On IBM
machines when netbooted we get BOOTP/DHCP reply use by IEEE1275 in
"bootppkt" property which allows us to easily, reliably and
automatically configure GRUB to continue loading from the same server
using same network parameters. However on my Sun Netra X1 I have to use
RARP and I haven't found the network boot configuration in device tree.
So my questions are:
1) Is there any way to retrieve client and server IP on sparc64 used by
IEEE1275 or do we have to redo RARP ourselves?
According to a web search newer sparc machines use BOOTP or DHCP instead
of or as an alternative to RARP.
2) Do they store bootp reply in some property?
3) If they don't is there a way to at least determine which protocol was
used (RARP, BOOTP or DHCP)?
Thank you in advance.

-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

             reply	other threads:[~2011-07-06 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 12:13 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-07-06 12:35 ` Determining boot server and own IP on sparc64-ieee1275 David Miller
2011-07-06 16:51   ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-07-06 16:17 ` Seth Goldberg

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=4E145160.2040203@gmail.com \
    --to=phcoder@gmail.com \
    --cc=davem@davemloft.net \
    --cc=grub-devel@gnu.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.