All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Guffens <guffens@auto.ucl.ac.be>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: network support
Date: Fri, 25 Mar 2005 10:08:47 +0100	[thread overview]
Message-ID: <4243D51F.6090604@auto.ucl.ac.be> (raw)
In-Reply-To: <87sm2kvhdp.fsf@student.han.nl>

Marco Gerards wrote:
> Vincent Guffens <guffens@auto.ucl.ac.be> writes:
> 
> Hi Vincent,
> 
> 
>>I just wanted to make a small update on the network support as I've
>>just had grub2 sending bootp request. Here is the request as seen from
>>my laptop directly connected to my test pc:
> 
> 
> Cool!  nice to hear about this progress.  I am sorry that I am slow
> with my replies.  Please keep hacking, I do care but I just have
> little time.
> 
> 
>>As for now, it compiles with as many warning as there are stars in the
>>sky but it at least, it does something.
>>
>>What I've done is as follows:
>>
>>     *  module : grub_pci
>>           o provided grub command : lspci, lspci_driver
> 
> 
> Is it possible to split this up like I described in a previous email?

basically, I think this is it. The lspci_driver does nothing when you 
load this module but the module exports the pci_register_driver which 
take a pci_driver structure and adds it to a linked list. Then, 
lspci_driver just goes through the list and display the driver name. 
Drivers are not yet inited.

> 
>>     * module : drv_*
>>           o provide grub command : none
>>           o description : driver from etherboot. Uses the
>>pci_register_driver to register itself and do nothing else
>>           o files: depends on the driver
> 
> 
> Would it be later to register other kinds of devices with
> pci_register_driver or is it very specific to NICs?

yes, all the etherboot drivers should just be fine after a small 
modification.

> 
>>     * module : pcimodprobe
>>           o provide grub command : ifconfig
>>           o description : initialises the nic, probes for the config
>>           o files :
> 
> 
> Config files?

Probing for the config here means looking for a dhcp server, obtaining 
an IP address, the gateway and the next-server. It does not yet look for 
the dhcp option-150 for the menu.

Now, at that point, the idea is that when you type a filename looking like

(nd0,tftp)/dir/file or (nd0)/dir/file

grub2 uses its IP address to contact the next-server with tftp to 
download the file /dir/file

For that purpose, I register a netfs file system. When the open method 
of the fs is called, the file is downladed and all the tftp blocks are 
stored in a linked list. The read method simply goes throught these 
blocks and reads a given lenght of data.

The tftp option in (nd0,tftp) is there for the future if we want to add 
some more download protocols like http or nfs as they do in etherboot.


> 
>>
>>The drivers are nearly no modified at all. I just changed
>>printf/grub_printf, added some #include and added the code to register
>>themselves.
> 
> 
> Ok, cool :)
> 
> Thanks,
> Marco
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
> 


-- 
				Vincent Guffens
				PhD Student UCL/CESAME
				tel:   +32 10 47 80 30
Value your freedom, or you will lose it, teaches history.
"Don't bother us with politics," respond those who don't want to learn.
	      	-- Richard M. Stallman



  reply	other threads:[~2005-03-25  9:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 10:33 network support Vincent Guffens
2005-03-11 12:22 ` Tobias Wollgam
2005-03-11 18:46 ` Marco Gerards
2005-03-11 20:09   ` Vincent Guffens
2005-03-12 13:40     ` Marco Gerards
2005-03-17 13:53       ` Vincent Guffens
2005-03-24 21:55         ` Marco Gerards
2005-03-25  9:08           ` Vincent Guffens [this message]
2005-03-25 12:07             ` Marco Gerards
2005-03-26  0:31               ` Yoshinori K. Okuji
2005-03-11 23:49 ` Yoshinori K. Okuji
2005-05-23 15:37 ` Tobias Wollgam
     [not found] <4293032C.3090404@inma.ucl.ac.be>
2005-05-25  9:31 ` Tobias Wollgam

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=4243D51F.6090604@auto.ucl.ac.be \
    --to=guffens@auto.ucl.ac.be \
    --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.