From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] add pattern based copy for ATF as already used for u-boot. This add support for different platforms where the binaries have different extension
Date: Tue, 12 Nov 2019 21:26:37 +0100 [thread overview]
Message-ID: <20191112212637.7c8721c2@windsurf> (raw)
In-Reply-To: <20191112201712.GA17609@curiosity>
On Tue, 12 Nov 2019 23:17:12 +0300
Sergey Matyukevich <geomatsi@gmail.com> wrote:
> > Hi,
> >
> > recently I've starting to make a little playground for using STM32MP1 (https://github.com/schenkmi/buildroot-op-tee-stm32mp1) with OP-TEE build with Buildroot. The proposed change is for platforms like the STM32MP1 which add some special headers to the final binary and add a different file ending. In the STM32MP1 the ATF binaries are called *.stm32. A similar change already exist for U-BOOT and optee-os but was missing for ATF.
>
> Hi Michael,
>
> Thanks for clarification. BTW, for some reason I don't see your patch
> in buildroot patchwork system. Though I am not sure if this is a
> problem for maintainers...
In fact, it seems like the initial e-mail from Michael didn't made it
to the list at all. At least, I don't see it in my local archives of
the mailing list.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-12 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1573221183-25905-1-git-send-email-michael.schenk@noser.com>
2019-11-11 8:51 ` [Buildroot] [PATCH 1/1] add pattern based copy for ATF as already used for u-boot. This add support for different platforms where the binaries have different extension Sergey Matyukevich
[not found] ` <DB7PR04MB500309181A711B70FEB5B58181740@DB7PR04MB5003.eurprd04.prod.outlook.com>
2019-11-12 20:17 ` Sergey Matyukevich
2019-11-12 20:26 ` Thomas Petazzoni [this message]
2019-11-14 13:29 Schenk Michael
2019-11-15 7:29 ` Sergey Matyukevich
2019-11-15 7:36 ` Yegor Yefremov
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=20191112212637.7c8721c2@windsurf \
--to=thomas.petazzoni@bootlin.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.