From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: GRUB and network (Re: GRUB and Google Summer of Code)
Date: Thu, 01 Apr 2010 23:06:27 +0200 [thread overview]
Message-ID: <4BB50AD3.2040904@gmail.com> (raw)
In-Reply-To: <201003301546.30857.trustlix@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
Alex Zanetti de Lima wrote:
> We discussed that with Vladimir, who pointed out the following drawbacks:
> 1) Current implementation was BOOTP/TFTP only. No support for other protocols.
> 2) Almost no shared code between architectures.
> 3) 100% dependent on OFW.
>
>
And it messed up with memory allocation since there is no way of
requesting only portion of file or know file size
> We are now working on a network infrastructure that could be shared by all
> platforms, including protocols, device drivers, etc. Gpxe project is a good
> start point, and most of things are being developed based on it.
>
> Chances are that we'll have something working on x86 soon, and then we'll start
> adding support for PPC (access to PCI bus via OFW, VIO, device drivers for some
> very specific cards like ehea, etc).
>
>
It's nice to hear.
But pay attention to license: not every piece of gpxe code is
license-compatible with grub2.
I would like to make an infrastructure for networking part of grub
itself since gpxe doesn't help much with configuration routines (this
part needs to be rewritten because gpxe environment is very different).
But the drivers imported from gpxe are likely to go into grub-extras.
Also high-level protocols like http have to be enhanced in grub since
gpxe implementation doesn't support seek even if protocol and server does.
When you or Manoel want to share something you're welcome to upload to
people or branches. It will allow easier collaboration and public review.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
prev parent reply other threads:[~2010-04-01 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 19:10 GRUB and Google Summer of Code Vladimir 'φ-coder/phcoder' Serbinenko
2010-03-30 14:31 ` Michal Suchanek
2010-03-30 17:26 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-03-30 18:46 ` Alex Zanetti de Lima
2010-04-01 16:11 ` Michal Suchanek
2010-04-01 20:59 ` GRUB and network (was Re: GRUB and Google Summer of Code) Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-02 0:12 ` Isaac Dupree
2010-04-02 12:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-01 21:06 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=4BB50AD3.2040904@gmail.com \
--to=phcoder@gmail.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.