All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: PXEgrub development on grub2
Date: Fri, 11 Sep 2009 15:17:09 +0200	[thread overview]
Message-ID: <20090911131709.GC7959@thorin> (raw)
In-Reply-To: <alpine.GSO.2.00.0909101417010.13483@oretfbsg.Jrfg.Fha.PBZ>

On Thu, Sep 10, 2009 at 02:17:56PM -0700, Seth Goldberg wrote:
>
>>> It sounds good. Looks like gPXE should work on EFI.
>>>
>>> I will try to build an image.
>>>
>>
>> Though that doestn't change that pxe.mod is currently only build for
>> i386-pc and nothing else
>
>  Does anyone have any patches that enable PXE on EFI-firmware-based systems?

What we need is firmware-independant support.  I can live with the PXE-on-BIOS
hack if it's useful, but what we're supposed to have is a driver framework like
the one in GRUB Legacy, not a stub for each firmware type.

Reliing on firmware is problematic, because it's usually proprietary and buggy,
we shouldn't do it if it can be avoided.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-09-11 13:17 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 14:07 PXEgrub development on grub2 Lars Nooden
2009-09-09 14:11 ` Felix Zielcke
2009-09-09 14:13   ` Lars Nooden
2009-09-09 15:04   ` Michal Suchanek
2009-09-09 19:40     ` Seth Goldberg
2009-09-10 12:39       ` Michal Suchanek
2009-09-10 13:01         ` Felix Zielcke
2009-09-10 21:17           ` Seth Goldberg
2009-09-11 13:17             ` Robert Millan [this message]
2009-09-11 21:07               ` Seth Goldberg
2009-09-12  0:05                 ` Michal Suchanek
2009-09-12  0:20                   ` Seth Goldberg
2009-09-12 12:54                 ` About firmware facilities Robert Millan
2009-09-13 20:54                   ` Seth Goldberg
2009-09-14 15:32                     ` Robert Millan
2009-09-14 18:57                       ` Brendan Trotter
2009-09-14 19:11                         ` Pavel Roskin
2009-09-14 20:12                           ` Brendan Trotter
2009-09-14 20:47                             ` Michal Suchanek
2009-09-14 20:49                             ` Vladimir 'phcoder' Serbinenko
2009-09-14 23:23                               ` Brendan Trotter
2009-09-14 23:43                                 ` Colin Watson
2009-09-14 23:56                                   ` Brendan Trotter
2009-09-15  0:28                                     ` Colin Watson
2009-09-15  1:06                                       ` Brendan Trotter
2009-09-15  8:59                                 ` Vladimir 'phcoder' Serbinenko
2009-09-15 16:01                                   ` Brendan Trotter
2009-09-19 14:06                                     ` Vladimir 'phcoder' Serbinenko
2009-09-20  9:04                                       ` Brendan Trotter
2009-09-20 10:38                                         ` Vladimir 'phcoder' Serbinenko
2009-09-19 21:07                           ` Robert Millan
2009-09-10 18:59     ` PXEgrub development on grub2 Robert Millan
2009-09-17 22:39       ` Joey Korkames
2009-09-18  6:19         ` Vladimir '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=20090911131709.GC7959@thorin \
    --to=rmh@aybabtu.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.