From: Gary Bisson <bisson.gary@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] package/mfgtools: drop package
Date: Mon, 10 Feb 2020 17:26:56 +0100 [thread overview]
Message-ID: <20200210162656.GD335587@p1g2.work> (raw)
In-Reply-To: <20200109191020.1282319-2-joerg.krause@embedded.rocks>
Hi Jorge,
On Thu, Jan 09, 2020 at 08:10:20PM +0100, J?rg Krause wrote:
> As suggested in [1] the package mfgtools is dropped.
>
> NXP did replaced the old mfgtools with the version number 0.2
> enterily with the uuu (Universal Update Utility) which is somehow
> named mfgtools 3.0 although the version scheme for the uuu tool is
> 1.xx.yyy.
>
> As the old mfgtools scripts are not compatible with the new uuu
> tool and as imx-uuu goes hand-in-hand with imx-uuc, which we ship
> for the target, the mfgtools package is dropped.
I know I'm the one who pushed for that commit to happen but now want to
mitigate the claim above.
True uuu depends on imx-uuc and mfgtools (1st of its name) too. BUT by
looking at imx-uuc, the two use cases are separated into 2 different
files:
- uu.c: daemon that uses utp protocol to communicate with host
- ufb.c: daemon that uses fastboot protocol to communicate with host
So I think it should be safe to have both host clients co-existing for
now. Maybe uu.c will be removed at some point in the future but I guess
NXP will leave it there for a while.
Regards,
Gary
next prev parent reply other threads:[~2020-02-10 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 19:10 [Buildroot] [PATCH v2 1/2] package/imx-uuu: new host package Jörg Krause
2020-01-09 19:10 ` [Buildroot] [PATCH v2 2/2] package/mfgtools: drop package Jörg Krause
2020-02-10 16:26 ` Gary Bisson [this message]
2020-04-13 20:24 ` Jörg Krause
2020-04-14 6:46 ` Gary Bisson
2020-04-14 7:47 ` Jörg Krause
2020-04-14 8:14 ` Gary Bisson
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=20200210162656.GD335587@p1g2.work \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox