From: Gary Bisson <bisson.gary@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] mfgtools: bump revision to latest uuu version
Date: Tue, 11 Jun 2019 10:15:59 +0200 [thread overview]
Message-ID: <20190611081559.GA24465@t450s.lan> (raw)
In-Reply-To: <cfe0721d-fbce-bb84-cf59-6353d7348ab8@mind.be>
Hi Arnout,
On Sat, Jun 08, 2019 at 10:28:09PM +0200, Arnout Vandecappelle wrote:
> Hi Gary,
>
> On 08/06/2019 12:53, Gary Bisson wrote:
> > NXP deprecated the old mfgtools code, also called mfgtools v2 although
> > the releases were named v0.xx.
> >
> > It has been replaced by the Universal Update Utility (uuu), also called
> > mfgtools v3.0 although the releases are named v1.x.yy.
> >
> > This new tool actually resides in the same repository in the master
> > branch whereas the old one is now in a 'linux' branch.
> >
> > Since the old tool has issues building lately, let's switch to the new
> > one. Note that uuu seems to be cleaner, supports much more features
> > (i.MX8/8M/8QXP boot, fastboot etc..) and has a better documentation:
> > https://github.com/NXPmicro/mfgtools/wiki
>
> Does it also offer the same API? If you have some scripts using mfgtools, will
> they work unchanged with uuu?
>
> If not, then I think uuu should be an entirely new package. We could choose to
> deprecate mfgtools immediately, but we'd need a legacy entry if the API has changed.
No the API has changed as the tool was apparently re-developed from the
ground up.
The idea of keeping the same package name although it broke the API is
that:
1- it's still in the same repository
2- NXP still mentions it as mfgtools (although sometimes calling it uuu)
-> all new NXP releases will use that new tool
> [snip]
> > +2. Run the MfgTools (now called uuu) client to boot the board from USB:
> >
> > +$ ./output/host/bin/uuu output/images/u-boot.imx
> [snip]
> > -$ ./host/bin/mfgtoolcli -l mmc -s uboot_defconfig=imx \
> > - -s dtbname=imx6q-sabrelite.dtb -s initramfs=rootfs.cpio.uboot \
> > - -s mmc=1 -p 1
>
> Yup, the API has definitely changed...
>
> So, I'm in favour of creating BR2_PACKAGE_HOST_UUU and killing
> BR2_PACKAGE_HOST_MFGTOOLS.
>
> I marked the patch as Not Applicable in patchwork. If you convince me to do it
> this way after all, we can fish it up again.
Ok I can do that. I'll offer another series that deprecates mfgtools and creates
a new uuu package.
Regards,
Gary
next prev parent reply other threads:[~2019-06-11 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 10:53 [Buildroot] [PATCH v3] mfgtools: bump revision to latest uuu version Gary Bisson
2019-06-08 20:28 ` Arnout Vandecappelle
2019-06-11 8:15 ` Gary Bisson [this message]
2019-06-11 9:52 ` Arnout Vandecappelle
2019-06-11 11:07 ` Thomas Petazzoni
2019-06-12 15:58 ` Yann E. MORIN
2019-06-12 16:41 ` Gary Bisson
2019-06-12 17:05 ` Yann E. MORIN
2019-06-08 20:28 ` Arnout Vandecappelle
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=20190611081559.GA24465@t450s.lan \
--to=bisson.gary@gmail.com \
--cc=buildroot@busybox.net \
/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.