From: Scott McNutt <scottm@orbacom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NFS support patch
Date: Tue, 24 Feb 2004 14:58:25 -0500 [thread overview]
Message-ID: <403BACE1.3010604@orbacom.com> (raw)
In-Reply-To: <403B7DB5.3010408@imc-berlin.de>
Steven,
> Fair enough so far. The length is correct. But
> apparently I did not get the correct data:
...
> What's the problem?
The packet wasn't copied correctly. Try this
patch. I tested with this patch on a PQ2FADS
board and everything looked good.
Regards,
--Scott
=> tftpboot 4000 u-boot.bin
Using FCC2 ETHERNET device
TFTP from server 192.168.0.40; our IP address is 192.168.0.99
Filename 'u-boot.bin'.
Load address: 0x4000
Loading: ########################################
done
Bytes transferred = 209720 (33338 hex)
=> nfs 40000 192.168.0.40:/tftpboot/u-boot.bin
Using FCC2 ETHERNET device
File transfer via NFS from server 192.168.0.40; our IP address is
192.168.0.99
Filename '/tftpboot/u-boot.bin'.
Load address: 0x40000
Loading: ########################################
done
Bytes transferred = 209720 (33338 hex)
=> cmp.b 4000 40000 33338
Total of 209720 bytes were the same
=>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: nfs-reply-len.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20040224/8309d3c3/attachment.txt
next prev parent reply other threads:[~2004-02-24 19:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 8:43 [U-Boot-Users] NFS support patch Masami Komiya
2004-02-24 1:27 ` Wolfgang Denk
2004-02-24 11:43 ` Steven Scholz
2004-02-24 14:32 ` Masami Komiya
2004-02-24 16:13 ` Detlev Zundel
2004-02-24 16:17 ` Steven Scholz
2004-02-24 22:36 ` Wolfgang Denk
2004-02-24 16:37 ` Steven Scholz
2004-02-24 19:58 ` Scott McNutt [this message]
2004-02-25 4:06 ` Masami Komiya
2004-02-25 9:01 ` Steven Scholz
2004-02-25 9:56 ` Masami Komiya
2004-02-26 23:56 ` 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=403BACE1.3010604@orbacom.com \
--to=scottm@orbacom.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 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.