All of lore.kernel.org
 help / color / mirror / Atom feed
From: NIIBE Yutaka <gniibe@m17n.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Networking status
Date: Tue, 10 Jan 2006 09:47:02 +0900	[thread overview]
Message-ID: <43C30406.1060906@m17n.org> (raw)
In-Reply-To: <8764ou330d.fsf@xs4all.nl>

Marco Gerards wrote:
> Things I planned to do:
>
> - Finish IPv4+UDP receive.
> - Implement DHCP/BOOTP.
> - Clean up the code a bit and document everything properly.
> - Add IEEE 1275 support (so networking will work on the PPC and
>   SPARC).
> - Implement TFTP.

FWIW, I developed a boot loader for M32R architecture which supports
HTTP download: http://www.gniibe.org/software/m32r-g00ff-20060107.tar.gz

It is single threaded, I mean, with polling (or busy loop).  It's only
for boot loader.

It supports both of IPv4 and IPv6.  ARP, Neighbour discovery of IPv6,
UDP, DHCP, DHCPv6, DNS, and HTTP/TCP is supported.

I know that TFTP is most popular for booting through the net.  But,
for our purpose (development of embedded system), HTTP is better.
People don't run TFTP server normally.  HTTP server is common, and put
a kernel on the web is easy thing to do.

If my code will be considered useful, I could transfer the copyright
to FSF (currently it's copyrighted by FSIJ).
-- 



  reply	other threads:[~2006-01-10  0:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 19:58 Networking status Marco Gerards
2006-01-10  0:47 ` NIIBE Yutaka [this message]
2006-01-10  3:30   ` Jun OKAJIMA
2006-01-10  4:15     ` NIIBE Yutaka
2006-01-10  9:59   ` Marco Gerards
2006-01-11  3:39     ` NIIBE Yutaka
2006-01-11 10:37       ` Marco Gerards

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=43C30406.1060906@m17n.org \
    --to=gniibe@m17n.org \
    --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.