From: Sascha Hauer <s.hauer@pengutronix.de>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: crc32 command
Date: Sat, 14 May 2011 19:16:07 +0200 [thread overview]
Message-ID: <20110514171607.GA30963@pengutronix.de> (raw)
In-Reply-To: <87d3jlkbb0.fsf@macbook.be.48ers.dk>
On Sat, May 14, 2011 at 09:09:55AM +0200, Peter Korsgaard wrote:
> >>>>> "Sascha" == Sascha Hauer <s.hauer@pengutronix.de> writes:
>
> >> How can I use crc32 to verify the files I transfer?
>
> Sascha> The algorithms differ, so cksum is not usable here. Got curious
> Sascha> myself and looked around in the net. the zip tool is usable for
> Sascha> this:
>
> Sascha> zip test.zip barebox.bin; unzip -lv test.zip
>
> Sascha> Ok, this sucks, but there is also a standalone program (haven't tested
> Sascha> this). See here:
>
> Sascha> http://docwiki.gumstix.org/index.php/Calculating_32_bit_CRCs
>
> The crc32 command is largely legacy from u-boot. Would there be interest
> in a cksum command (it's afaik just like the normal crc32 except it also
> uses the length) or md5/sha1/sha256sum? We have all the infrastructure,
> so it should be easy to add.
md5sum would be very useful. Would it add much to the binary space?
(If yes, that would be no reason to not have it, but probably more
boards will enable this when it's small)
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-05-14 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 15:54 Benoît Burnichon
2011-05-13 17:22 ` Sascha Hauer
2011-05-14 7:09 ` Peter Korsgaard
2011-05-14 17:16 ` Sascha Hauer [this message]
2011-05-14 21:50 ` Peter Korsgaard
2011-05-15 8:50 ` Alexey Galakhov
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=20110514171607.GA30963@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jacmet@sunsite.dk \
/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