From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Tue, 13 May 2008 22:05:29 -0400 Subject: [U-Boot-Users] How to use tftp to book kernel image and mount remote root fs In-Reply-To: References: <20080513060732.14EE12476E@gemini.denx.de> Message-ID: <482A48E9.3060609@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Steven Woody wrote: > On Tue, May 13, 2008 at 2:07 PM, Wolfgang Denk wrote: >> Dear Steven, >> >> in message you wrote: >>> Q1: >>> >>> Both 5.9.5.1 ( > http://www.denx.de/wiki/view/DULG/UBootCmdGroupDownload#Section_5.9.5.1. >>> ) and 5.9.5.6 ( >>> http://www.denx.de/wiki/view/DULG/UBootCmdGroupDownload#Section_5.9.5.6. >>> ) talk about booting image via network, but there are only few lines >>> of description about these commands. I don't know which one I should >>> use, tftpboot or bootp? And, for each one, what's the requirement on >> That depends on what you want to do. Do you understand the differecne >> between TFTP and BOOTP (resp. DHCP) protocols? > > I understand tftp and bootp as a function of current DHCP, but I don't > know how tftp and bootp is related. Would you suggest me something to > read? Thank you. Bootp is a boot protocol that allows a system to query a server to figure out what IP it is assigned and what executable file to load (typically via TFTP). DHCP is the successor to bootp. TFTP is a file transfer protocol that allows a system to load its executable (typically) file from the server. (ignore RARP, it is deprecated). HTH, gvb