From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] test.py and tftp crc32 test?
Date: Mon, 15 Aug 2016 18:49:40 -0400 [thread overview]
Message-ID: <20160815224940.GC5342@bill-the-cat> (raw)
Hey guys,
Is anyone else running the crc32 tftp tests with test.py? I'm trying to
do it locally but even with a 2MiB file it looks like somehow the crc32
is never captured in the output. I've already made sure that the crc32
value is in lowercase to match the U-Boot output and running the test
steps in console gives me the expected output. And the rest of the
network tests pass, any ideas? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160815/c8262136/attachment.sig>
next reply other threads:[~2016-08-15 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 22:49 Tom Rini [this message]
2016-08-15 22:59 ` [U-Boot] test.py and tftp crc32 test? Stephen Warren
2016-08-15 23:20 ` Tom Rini
2016-08-16 3:35 ` Stephen Warren
2016-08-16 5:19 ` Heiko Schocher
2016-08-16 11:55 ` Tom Rini
2016-08-16 5:14 ` Heiko Schocher
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=20160815224940.GC5342@bill-the-cat \
--to=trini@konsulko.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