From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.33) id 1Bg6aH-0001iD-0r for mharc-grub-devel@gnu.org; Thu, 01 Jul 2004 14:46:57 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Bg6aF-0001hN-Km for grub-devel@gnu.org; Thu, 01 Jul 2004 14:46:55 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Bg6aD-0001gy-L3 for grub-devel@gnu.org; Thu, 01 Jul 2004 14:46:55 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bg6aD-0001go-IO for grub-devel@gnu.org; Thu, 01 Jul 2004 14:46:53 -0400 Received: from [193.45.208.6] (helo=griffin.skarpodata.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1Bg6Y5-0006RM-KS for grub-devel@gnu.org; Thu, 01 Jul 2004 14:44:42 -0400 Received: from bushwacker (183.201.216.81.s-s.siw.siwnet.net [81.216.201.183]) by griffin.skarpodata.com (8.12.10/8.12.10) with SMTP id i61K97kL025798; Thu, 1 Jul 2004 22:09:09 +0200 Date: Thu, 1 Jul 2004 20:44:30 +0200 From: Johan Rydberg To: The development of GRUB 2 Message-Id: <20040701204430.19e43165.jrydberg@night.trouble.net> In-Reply-To: <87d63falyb.fsf@marco.marco-g.com> References: <200406281125.03655.okuji@enbug.org> <87fz8ezjo9.fsf@marco.marco-g.com> <200407011332.42252.okuji@enbug.org> <87d63falyb.fsf@marco.marco-g.com> X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: calling UNDI API X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2004 18:46:55 -0000 Marco Gerards wrote: : > GRUB doesn't assume that hardware interrupts occur during normal : > execution, since this makes the implementation very complex, due to : > the switch between real mode and protected mode on i386. So I prefer : > the polling approach to the interruption-based approach. For this, : > Etherboot fits gracefully. : : Ok, I agree. Isn't GRUB executing in protected mode, except when it escapes into real mode to do BIOS calls? I can not see how it would be difficult to use interrupts in such context. Or does the BIOS depend on interrupst? : > BTW, do you really need TCP in GRUB? I know some people want to use TCP : > protocols for netboot, such as HTTP and FTP. But I feel this is : > overkill. If you need only UDP, it's quite easy to implement. You can : > just copy the code from GRUB Legacy with a few modifications for : > portability. : : No, I just said TCP/IP because I am used to it and it is the name of : the protocol, I did not mean TCP specifically. But I know a lot of : people would like TCP support. It is at least an option that should : be left open, IMHO. The problem is that TCP is rather interrupt driven by nature. For example, it uses a lot of timers for packet re-sending and similar stuff. Maybe it is possible to use lwIP, which is released under a modified BSD license. See http://savannah.nongnu.org/projects/lwip/ ~j