From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH v2 1/1] dfu: remove UPDATE_TFTP
Date: Fri, 28 Aug 2020 11:21:12 +0200 [thread overview]
Message-ID: <20200828112112.7383a68a@jawa> (raw)
In-Reply-To: <11344f5a-cfc1-bea0-0741-f0fdf427619d@denx.de>
Hi Marek,
> On 8/28/20 4:32 AM, Heinrich Schuchardt wrote:
> > On 7/21/20 8:02 PM, Heinrich Schuchardt wrote:
> >> Using UPDATE_TFTP the firmware can be updated from TFTP by writing
> >> to NOR flash. The same is possible by defining a dfu command in
> >> CONFIG_PREBOOT.
> >>
> >> The dfu command cannot only write to NOR but also to other
> >> devices. In README.dfutfp UPDATE_TFTP has been marked as
> >> deprecated. It is not used by any board.
> >>
> >> Remove TFTP update via CONFIG_UPDATE_TFTP.
> >>
> >> Adjust the documentation.
> >>
> >> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> >> ---
> >> v2:
> >> rework the documentation
> >
> > On 8/28/20 12:17 AM, Marek Vasut wrote (in reply to a pull
> > request):
> >> Also note that the UPDATE_TFTP is being actively used, why is it
> >> removed here and this late in rc3 ? I think these patches should
> >> really be postponed until after the release.
> >
> > Hello Marek,
>
> Hi,
>
> > do you see a problem in principal with the removal of UPDATE_TFTP
> > which is redundant to what you can do with DFU or is it only the
> > timing issue?
>
> I don't see how it is redundant. The usecase I see is a fitImage which
> contains the update fragments is applied with a single command this
> way. I don't see a suitable replacement.
It is good that it now is clear that there is a use case for it - so
more discussion is needed.
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200828/f3728749/attachment.sig>
prev parent reply other threads:[~2020-08-28 9:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 18:02 [PATCH v2 1/1] dfu: remove UPDATE_TFTP Heinrich Schuchardt
2020-08-28 2:32 ` Heinrich Schuchardt
2020-08-28 8:42 ` Marek Vasut
2020-08-28 9:11 ` Heinrich Schuchardt
2020-08-28 9:45 ` Marek Vasut
2020-08-28 10:00 ` Lukasz Majewski
2020-08-28 10:03 ` Marek Vasut
2020-08-28 11:49 ` Lukasz Majewski
2020-08-28 12:20 ` Tom Rini
2020-10-15 6:30 ` CONFIG_UPDATE_TFTP Heinrich Schuchardt
2020-10-15 12:40 ` CONFIG_UPDATE_TFTP Marek Vasut
2020-10-15 12:48 ` CONFIG_UPDATE_TFTP Heinrich Schuchardt
2020-10-15 13:05 ` CONFIG_UPDATE_TFTP Marek Vasut
2020-08-28 9:21 ` Lukasz Majewski [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=20200828112112.7383a68a@jawa \
--to=lukma@denx.de \
--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