From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [RFC] dfu: remove UPDATE_TFTP
Date: Wed, 15 Jul 2020 15:23:38 +0200 [thread overview]
Message-ID: <20200715152338.48f7fcc4@jawa> (raw)
In-Reply-To: <eba775ca-f76c-ee12-b1fa-2e3751c9bd93@gmx.de>
Hi Heinrich,
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 15.07.20 13:24, Lukasz Majewski wrote:
> > Hi Heinrich,
> >
> >> 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.
> >
> > Could you also write in the proper README the steps necessary to
> > have the same functionality as with UPDATE_TFTP with dfu and
> > preboot? I think that it would be good to have it written down in
> > ./doc.
> >
>
> doc/README.dfutftp already describes the necessary steps as:
>
> * enable CONFIG_DFU_TFTP
> * enable CONFIG_PREBOOT
> * put a string like "dfu tftp 0 mmc 0" into the "preboot" env variable
>
> Do you want me to explicitly write that "dfu tftp 0 mtd 0" replaces
> the former auto-update functionality?
No, this is fine. Thanks.
>
> Best regards
>
> Heinrich
>
>
> >> It is not used by any board.
> >>
> >> Remove tFTP update via CONFIG_UPDATE_TFTP.
> >>
> >> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> ---
> >> Currently Gitlab CI lacks a test for dfu tftp. I will try to set
> >> one up. When it is properly tested I will send a final patch
> >> series. But beforehand I would like to know if eliminating
> >> UPDATE_TFTP is ok.
> >>
> >> Best regards
> >>
> >> Heinrich
> -----BEGIN PGP SIGNATURE-----
>
> iQIzBAEBCAAdFiEEbcT5xx8ppvoGt20zxIHbvCwFGsQFAl8O7SYACgkQxIHbvCwF
> GsSp9RAAkNdFFkYpaSit5367azX56eAt4eiHyD1bqCEYJB1Z3+f3P0xM0NjD2B+T
> QNVHHNbE+fvEftCT5Sl28mZIhqTpqZnMv5TFAyj4c1NxEmHnBFoeQcNb9vqzNaX3
> 8txdrYV3Nx5fKZlFDa2NqX0/+2NMx4DjqnN2P71IaFrp98qQMR0b62OQOAR9CwNE
> YEW+usIRyE/cPHvvYMzKTS/8e/jJTRQXtFJvFjU3xh3/4s4/fbQCIbJZwMACsMrJ
> hYAoT0d2+VNWBEg/i0q/uUmUh5OuwnrSsYaI3MdqV5DpNHcsF6UTOhT6svE+MibV
> v4gMO7D2yfX7Zob6cLGU9hmnio32U0xx4jRhWNZtphuX1mI4psKtZp5k9FdRGjgn
> +hrbkjG1y8xbytFiw5quCk07E34x8AttHDDM76wF5wu7WrH0U4HBjoNucj9Q2S6j
> ZBD3IP/bOwpO3x32tpcFid+GaWy7NRTQ6OtOL4jF/Qgjk7F714wP1N5+cO4qB+kF
> QFaRw+4zOGo0W0DLD9WyexDuY7QyNDbfXYOE6ao/pXGfFfWCa2WJCt0JUv1TnH5L
> AbCqaNILWDZDJ0YBaPjJCqbeiikCG859nr/AgEPR8ns8jJ2i/2ditk9yUuha27Ub
> mLBjbhV9PYo+5K07xMkVis+DIIgCc3xOJtL8DoviiJMO0xLBKos=
> =IzXA
> -----END PGP SIGNATURE-----
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/20200715/1215cead/attachment.sig>
next prev parent reply other threads:[~2020-07-15 13:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 10:45 [RFC] dfu: remove UPDATE_TFTP Heinrich Schuchardt
2020-07-15 11:24 ` Lukasz Majewski
2020-07-15 11:49 ` Heinrich Schuchardt
2020-07-15 13:23 ` Lukasz Majewski [this message]
2020-07-15 14:06 ` Michal Simek
2020-07-15 14:42 ` Heinrich Schuchardt
2020-07-15 14:48 ` Michal Simek
2020-07-21 3:03 ` Heinrich Schuchardt
2020-07-21 6:31 ` Michal Simek
2020-07-16 1:52 ` AKASHI Takahiro
2020-07-16 4:44 ` Heinrich Schuchardt
2020-07-21 11:56 ` AKASHI Takahiro
2020-07-16 1:36 ` AKASHI Takahiro
2020-07-16 4:13 ` Heinrich Schuchardt
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=20200715152338.48f7fcc4@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 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.