From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] patch to add autoload via NFS
Date: Wed, 25 Feb 2004 14:29:07 +0100 [thread overview]
Message-ID: <403CA323.7010109@imc-berlin.de> (raw)
In-Reply-To: <403C9E50.6000402@sonare.it>
Masami Komiya wrote:
> The patch to add autoload via NFS after bootp or dhcp.
>
> If you want to use, please define CONFIG_AUTOLOAD_VIA_NFS
> in your configuration file.
>
> What do you think about this patch ? (although I don't need
> autoload so much.)
Hmm. If you do it this way you can't have autoload enabled for both
NFS and TFTP! Is that a good thing?
Is there a way the DHCP server can tell the client how to load the
file? I.e. to use tftp or nfs or something else? So you can decide
based answer from the DHCP server how to load it...
--
Steven Scholz
next prev parent reply other threads:[~2004-02-25 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 13:08 [U-Boot-Users] patch to add autoload via NFS Masami Komiya
2004-02-25 13:29 ` Steven Scholz [this message]
2004-02-25 14:27 ` Masami Komiya
2004-02-25 14:34 ` Steven Scholz
2004-02-25 15:54 ` Masami Komiya
2004-02-26 4:11 ` Masami Komiya
2004-02-26 9:34 ` Wolfgang Denk
2004-02-26 11:51 ` Masami Komiya
2004-02-27 0:24 ` Wolfgang Denk
2004-02-26 9:33 ` Wolfgang Denk
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=403CA323.7010109@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--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