From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Ymodem error checking
Date: Sun, 03 Jul 2005 15:56:00 -0000 [thread overview]
Message-ID: <1120406181.11779.22.camel@localhost.localdomain> (raw)
In-Reply-To: <1120403887.31874.65.camel@hermes>
> Each [relatively small] record in the Y-modem protocol contains
> a simple checksum. This must match for the packet to be ACK'd
> Also, packets are numbered and will only be accepted in the proper
> order. This level of checking is sufficient (at least 99% of the
> time IMHO)
OK. Thanks.
It seems to me that there are many other things to worry about before
false successes from Ymodem uploads show up on the radar.
--
Øyvind Harboe
http://www.zylin.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-07-03 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 14:39 Øyvind Harboe
2005-07-03 15:18 ` Gary Thomas
2005-07-03 15:56 ` Øyvind Harboe [this message]
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=1120406181.11779.22.camel@localhost.localdomain \
--to=oyvind.harboe@zylin.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gary@mlbassoc.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).