From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Luca Ceresoli <luca@lucaceresoli.net>,
Julien Olivain <juju@cotds.org>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/zynq-boot-bin: port to python3 and move to support/scripts
Date: Mon, 10 Jan 2022 23:28:08 +0100 [thread overview]
Message-ID: <20220110222808.GU1477939@scaer> (raw)
In-Reply-To: <CADvTj4qnuwUh594-QC-4ySNQX2aSfhfs36tX-cH5vMB52EbgbQ@mail.gmail.com>
James, All,
On 2022-01-10 15:18 -0700, James Hilliard spake thusly:
> On Mon, Jan 10, 2022 at 3:10 PM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
[--SNIP--]
> > So I wonder if it even makes sense to keep package/zynq-boot-bin now.
> Well if someone is using an older uboot that doesn't have the
> generation capability
> integrated then it's probably still needed right?
But then, they would have that tool in their uboot tree, and then
nothing would prevent them from running it as a post-build (or
post-image) script.
Yes, they would need to have a python2 on their host. But that will be
the case if they stick to such older tools which may break on more
recent systems, not just uboot...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-10 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 20:26 [Buildroot] [PATCH 1/1] package/zynq-boot-bin: port to python3 and move to support/scripts James Hilliard
2021-12-31 21:28 ` Yann E. MORIN
2021-12-31 21:48 ` James Hilliard
2022-01-10 22:10 ` Yann E. MORIN
2022-01-10 22:18 ` James Hilliard
2022-01-10 22:28 ` Yann E. MORIN [this message]
2022-01-10 22:31 ` James Hilliard
2022-01-10 22:46 ` Luca Ceresoli
2022-01-10 22:55 ` James Hilliard
2022-01-11 9:10 ` Luca Ceresoli
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=20220110222808.GU1477939@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=juju@cotds.org \
--cc=luca@lucaceresoli.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.