All of lore.kernel.org
 help / color / mirror / Atom feed
From: vincent guffens <v.guffens@imperial.ac.uk>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: pci support
Date: Sat, 06 May 2006 16:12:46 +0100	[thread overview]
Message-ID: <445CBCEE.8050906@imperial.ac.uk> (raw)
In-Reply-To: <87ejz7b48h.fsf@xs4all.nl>

Marco Gerards wrote:
> vincent guffens <v.guffens@imperial.ac.uk> writes:
> 
> Hi Vincent,
> 
> 
>>I was wondering if there was still an interest in pci support as
>>discussed previously. That is a general interface exported by a module
>>such as
> 
> 
> Yes, that will make it possible to implement all kinds of drivers and
> make something like lspci possible.
> 
> Sorry I still didn't start working on the networking stuff as planned.
> Scripting and other stuff occupies me longer than I originally
> expected. :)

Sure, no problem! In fact, I was wondering if it would be possible to
have a discussion about the overall networking strategy that will be put
in place for grub2 (and which is schedulled for the next release !).

As I understand, supporting the etherboot drivers is no longer the
primary option. As it is out of the question to have its own set of
driver,  the UNDI driver seems like a good idea. However, UNDI support
would constrain significantly the design of the network stack. In
particular, it defines a lot of structure such as dhcp header, ipv4
addresses and so on. It also involves interruption while it was assumed
previously that the interfaces would be polled.

There is also the option of calling etherboot from grub2, which seems
quite appealing but I think I don't really quite get that.

cheers!








  reply	other threads:[~2006-05-06 15:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-06 13:36 pci support vincent guffens
2006-05-06 14:08 ` Vesa Jääskeläinen
2006-05-06 14:46 ` Marco Gerards
2006-05-06 15:12   ` vincent guffens [this message]
2006-05-06 16:12     ` Marco Gerards
2006-05-06 16:25       ` vincent guffens
2006-05-06 17:07         ` Marco Gerards
  -- strict thread matches above, loose matches on Subject: below --
2008-01-28 14:03 PCI support Marco Gerards
2008-01-28 17:25 ` Robert Millan
2008-01-28 18:32   ` Marco Gerards
2008-01-28 19:08     ` Robert Millan
2008-01-29  8:40       ` Marco Gerards
2008-01-30 17:57 ` Marco Gerards
2008-01-30 18:44   ` Robert Millan
2008-01-30 20:08     ` Marco Gerards
2008-01-30 22:01       ` Robert Millan
2008-01-30 22:17         ` Marco Gerards
2008-01-30 22:25           ` Robert Millan
2008-01-31  8:51             ` Marco Gerards
2008-01-31 11:05               ` Robert Millan
2008-02-02 15:39                 ` Marco Gerards
2008-01-30 19:40   ` Yoshinori K. Okuji
2008-01-30 20:07     ` Marco Gerards
2001-10-12 18:38 Kevin Fry
2001-10-12 19:09 ` Dan Taylor

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=445CBCEE.8050906@imperial.ac.uk \
    --to=v.guffens@imperial.ac.uk \
    --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.