From: Wolfgang Denk <wd@denx.de>
To: "Pali Rohár" <pali@kernel.org>
Cc: Simon Glass <sjg@chromium.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/2] xyz-modem: Wait infinitely for initial y-modem packet
Date: Mon, 13 Sep 2021 14:12:54 +0200 [thread overview]
Message-ID: <1332387.1631535174@gemini.denx.de> (raw)
In-Reply-To: <20210913110806.27hc36n6gmhw6uq4@pali>
Dear Pali Rohár,
In message <20210913110806.27hc36n6gmhw6uq4@pali> you wrote:
>
> > If you use loady in any kind of scripts, this would now hard hang
> > the system, while until now it was possible to recover from the
> > error.
>
> Yes, this is a good point. But on the other hand, 'loadb' and 'loads'
> commands already have this behavior. So question is if it is better to
> have same behavior in all 'load?' commands or each 'load?' would behave
> differently... Because for software which transmit files and supports
> more protocols (e.g. both x-modem and kermit) it may be a nightmare if
> receiver behaves differently...
Yes, you are right, there is an unlucky difference in behaviour.
But all these interfaces are pretty old, and I would not invest
efforts to fix a aproblem nobody ever noticed before, at the risk
of breaking existing stuff.
I wonder if there are any users of 'loads' left - the Motorola
S-record format is close to 50 years old and cumbersome to use. I
can't even remeber when I used it the last time - must be 15+ years
or such.
'loadb" is a different thing, but there you usually have kermit on
the other side, and usually run an interactive session (or an
automated one using something like tbot ) - in any case, you
normally have to interact on both sides.
I never had a problem wih the current behaviour there.
> If you do not have integrated y-modem support in your terminal you have
> to do:
>
> 1) open terminal and write 'loady' into U-Boot console
> 2) disconnect terminal
> 3) start y-modem software
> 4) choose file to transmit
> 5) instruct y-modem software to start transfer
>
> And if 'loady' timeouts between 2) - 5) then it returns back to the
If this happens, the timeout is inconveniently short of you are too
slow. I think what would be helpful is to make the timeout
adjustable (env var).
> So... I do not know what is better if current behavior or this new which
> changes UI interaction.
We can do both, and still solve your problem: make the timeout
adjustable so you can set it to something you can conveniently work
with.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"I can call spirits from the vasty deep."
"Why so can I, or so can any man; but will they come when you do call
for them?" - Shakespeare, 1 King Henry IV, Act III, Scene I.
next prev parent reply other threads:[~2021-09-13 12:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 20:46 [PATCH 1/2] xyz-modem: Wait infinitely for initial y-modem packet Pali Rohár
2021-09-10 20:46 ` [PATCH 2/2] xyz-modem: Wait infinitely for initial x-modem packet Pali Rohár
2021-09-13 10:43 ` Wolfgang Denk
2021-09-13 10:42 ` [PATCH 1/2] xyz-modem: Wait infinitely for initial y-modem packet Wolfgang Denk
2021-09-13 11:08 ` Pali Rohár
2021-09-13 12:12 ` Wolfgang Denk [this message]
2021-09-13 12:22 ` Pali Rohár
2021-09-13 13:02 ` Wolfgang Denk
2022-08-27 11:50 ` Pali Rohár
2021-09-13 14:32 ` Tom Rini
2022-08-27 11:48 ` [PATCH v2] xyz-modem: Allow to configure initial timeout for loadx and loady Pali Rohár
2022-08-27 12:53 ` Tom Rini
2022-08-27 12:56 ` Pali Rohár
2022-08-27 14:30 ` Tom Rini
2022-08-27 14:32 ` Pali Rohár
2022-08-27 14:41 ` Tom Rini
2022-08-27 14:47 ` Pali Rohár
2022-08-29 14:54 ` Heinrich Schuchardt
2022-08-27 14:37 ` [PATCH v3] " Pali Rohár
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=1332387.1631535174@gemini.denx.de \
--to=wd@denx.de \
--cc=pali@kernel.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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.