From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] How to use tftp to book kernel image and mount remote root fs
Date: Tue, 13 May 2008 22:05:29 -0400 [thread overview]
Message-ID: <482A48E9.3060609@gmail.com> (raw)
In-Reply-To: <ed4892840805122334p3df7cc1bvab9caf188892f1d@mail.gmail.com>
Steven Woody wrote:
> On Tue, May 13, 2008 at 2:07 PM, Wolfgang Denk <wd@denx.de> wrote:
>> Dear Steven,
>>
>> in message <ed4892840805121852t46d4c4d0rd52a9eb129121f7b@mail.gmail.com> 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.
<http://www.linuxjournal.com/article/5465> (ignore RARP, it is deprecated).
HTH,
gvb
next prev parent reply other threads:[~2008-05-14 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 10:02 [U-Boot-Users] How to use tftp to book kernel image and mount remote root fs Steven Woody
2008-05-12 18:29 ` Wolfgang Denk
2008-05-13 1:52 ` Steven Woody
2008-05-13 6:07 ` Wolfgang Denk
2008-05-13 6:34 ` Steven Woody
2008-05-14 2:05 ` Jerry Van Baren [this message]
2008-05-14 2:30 ` Steven Woody
2008-05-14 3:52 ` Jerry Van Baren
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=482A48E9.3060609@gmail.com \
--to=gvb.uboot@gmail.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox