All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manoel Rebelo Abranches <mrabran@linux.vnet.ibm.com>
To: grub-devel@gnu.org
Subject: Network branch
Date: Tue, 17 May 2011 08:43:31 -0300	[thread overview]
Message-ID: <4DD25F63.3070007@linux.vnet.ibm.com> (raw)

I'm working in a NET branch 
(http://bzr.savannah.gnu.org/r/grub/branches/net/) and have submitted 
some patches for network booting using tftp protocol and Open Firmware 
as the card driver (the implementation is sufficiently generic to 
utilize usual card drivers). This has been tested in P5, P6 and P7.

Although these patches were still not reviewed they have some great 
advantages when compared with yaboot:


1 - We can set larger block sizes (and then get larger files), a 
limitation in some firmware versions.
2 - Less memory usage. In yaboot the file is all downloaded in a buffer 
before is efectivelly used. Due to some file abstractions the file is 
nearly doubled in memory. In GRUB we free the memory used by the packets 
already read,then much less memory is necessary (useful in some big 
INITRD files).
3 - Better user interface.


This version is already very stable and I did many tests and fixed some 
bugs (in our lab there are some people already using it instead of yaboot)
We still have to add support for PXE using UNDI. If someone would like 
to help in this regard, I will try to look at it in the near future.

Some things that still have to be done:


1 - Support for PXE.
2 - Support for ipv6.
3 - Other protocols beside TFTP, like DHCP and TCP based protocols.

-- 
Best regards,

Manoel R. Abranches
Software Engineer - LTC - IBM - Brazil



             reply	other threads:[~2011-05-17 11:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 11:43 Manoel Rebelo Abranches [this message]
2011-05-19 13:40 ` Network branch Vladimir 'φ-coder/phcoder' Serbinenko

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=4DD25F63.3070007@linux.vnet.ibm.com \
    --to=mrabran@linux.vnet.ibm.com \
    --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.