From: Gary Bisson <gary.bisson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] imx-mkimage: new package
Date: Mon, 19 Feb 2018 17:44:06 +0100 [thread overview]
Message-ID: <20180219164406.GA22465@t450s.lan> (raw)
In-Reply-To: <20180218155100.3e4e090f@windsurf>
Hi Thomas, Erik,
On Sun, Feb 18, 2018 at 03:51:00PM +0100, Thomas Petazzoni wrote:
> Hello,
>
> Thanks for this contribution!
>
> On Sun, 18 Feb 2018 14:28:29 +0100, Erik Larsson wrote:
> > Signed-off-by: Erik Larsson <karl.erik.larsson@gmail.com>
> > ---
> > package/Config.in.host | 1 +
> > .../0001-make-bl33-read-env-variables.patch | 37 ++++++++++++++++++++++
> > package/freescale-imx/imx-mkimage/Config.in.host | 5 +++
> > package/freescale-imx/imx-mkimage/imx-mkimage.hash | 3 ++
> > package/freescale-imx/imx-mkimage/imx-mkimage.mk | 23 ++++++++++++++
> > 5 files changed, 69 insertions(+)
> > create mode 100644 package/freescale-imx/imx-mkimage/0001-make-bl33-read-env-variables.patch
> > create mode 100644 package/freescale-imx/imx-mkimage/Config.in.host
> > create mode 100644 package/freescale-imx/imx-mkimage/imx-mkimage.hash
> > create mode 100644 package/freescale-imx/imx-mkimage/imx-mkimage.mk
> >
> > diff --git a/package/Config.in.host b/package/Config.in.host
> > index 199a8e9..b1cfa75 100644
> > --- a/package/Config.in.host
> > +++ b/package/Config.in.host
> > @@ -15,6 +15,7 @@ menu "Host utilities"
> > source "package/e2fsprogs/Config.in.host"
> > source "package/e2tools/Config.in.host"
> > source "package/faketime/Config.in.host"
> > + source "package/freescale-imx/imx-mkimage/Config.in.host"
>
> I'm not sure this package needs to be under package/freescale-imx/.
> This sub-directory was initially created to share the
> FREESCALE_IMX_SITE and FREESCALE_IMX_EXTRACT_HELPER definitions, but
> you don't use them.
Actually there are plenty of packages in that folder that don't need the
extract helper nor the site address. Would you like those moved out of
it? (imx-kobs, imx-uuc, imx-vpuwrap etc..).
As a user I find it convenient to have it all in one place but I'd
understand moving them around.
Another aspect of that folder is BR2_PACKAGE_FREESCALE_IMX_PLATFORM,
although it is accessible at other places, which has an effect on which
packages are available.
> > diff --git a/package/freescale-imx/imx-mkimage/0001-make-bl33-read-env-variables.patch b/package/freescale-imx/imx-mkimage/0001-make-bl33-read-env-variables.patch
> > new file mode 100644
> > index 0000000..490eb05
> > --- /dev/null
> > +++ b/package/freescale-imx/imx-mkimage/0001-make-bl33-read-env-variables.patch
> > @@ -0,0 +1,37 @@
> > +From 5ca549356ef889286c12b4d736d9026efafb8fff Mon Sep 17 00:00:00 2001
> > +From: Erik Larsson <erik.larsson@combitech.se>
> > +Date: Mon, 29 Jan 2018 08:00:57 +0100
> > +Subject: [PATCH] Add support for overriding BL32 and BL33 not only BL31
> > +
> > +Signed-off-by: Erik Larsson <karl.erik.larsson@gmail.com>
> > +Signed-off-by: Christopher Dahlberg <crille.dahlberg@gmail.com>
> > +Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
>
> What is the upstream status of this patch ?
>
> > diff --git a/package/freescale-imx/imx-mkimage/Config.in.host b/package/freescale-imx/imx-mkimage/Config.in.host
> > new file mode 100644
> > index 0000000..3cf0966
> > --- /dev/null
> > +++ b/package/freescale-imx/imx-mkimage/Config.in.host
> > @@ -0,0 +1,5 @@
> > +config BR2_PACKAGE_HOST_IMX_MKIMAGE
> > + bool "host imx-mkimage"
> > + help
> > + imx-mkimage is used to combine input images and generate
> > + final boot image with appropriate IVT set.
>
> We like to have a blank line, and then the URL of the upstream project
> main page. Here, https://source.codeaurora.org/external/imx/imx-mkimage
> might be enough, unless there is a better page.
>
> > diff --git a/package/freescale-imx/imx-mkimage/imx-mkimage.mk b/package/freescale-imx/imx-mkimage/imx-mkimage.mk
> > new file mode 100644
> > index 0000000..a5b1f93
> > --- /dev/null
> > +++ b/package/freescale-imx/imx-mkimage/imx-mkimage.mk
> > @@ -0,0 +1,23 @@
> > +################################################################################
> > +#
> > +# imx-mkimage
> > +#
> > +################################################################################
> > +
> > +IMX_MKIMAGE_VERSION = imx_4.9.51_imx8m_beta
> > +IMX_MKIMAGE_SITE = https://source.codeaurora.org/external/imx/imx-mkimage
> > +IMX_MKIMAGE_SITE_METHOD = git
> > +IMX_MKIMAGE_LICENSE = GPL-2.0
> > +IMX_MKIMAGE_LICENSE_FILES = iMX8dv/COPYING
> > +
> > +define HOST_IMX_MKIMAGE_BUILD_CMDS
> > + $(MAKE) -C $(@D)/iMX8M -f soc.mak mkimage_imx8
>
> Why are you building just the tool in iMX8M ? There is also one in src/
> and in iMX8dv. What are the differences ? Should we build/install all
> of them ? Conditionally ?
That is where new BR2_PACKAGE_FREESCALE_IMX_PLATFORM values would be
needed to separate iMX8M, iMX8QM and iMX8QX.
As a FYI, iMX8dv was some sort of development version of i.MX8, this
will not be supported moving forward, only the 3 families listed above.
Regards,
Gary
next prev parent reply other threads:[~2018-02-19 16:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 13:28 [Buildroot] [PATCH 0/3] Initial support for NXP iMX8 (imx8mq-evk) Erik Larsson
2018-02-18 13:28 ` [Buildroot] [PATCH 1/3] imx-mkimage: new package Erik Larsson
2018-02-18 14:51 ` Thomas Petazzoni
2018-02-19 5:43 ` Erik Larsson
2018-02-19 8:02 ` Thomas Petazzoni
2018-02-19 8:05 ` Erik Larsson
2018-02-19 9:55 ` Marcus Folkesson
2018-02-19 16:44 ` Gary Bisson [this message]
2018-02-19 16:55 ` Thomas Petazzoni
2018-02-19 10:00 ` Marcus Folkesson
2018-02-18 13:28 ` [Buildroot] [PATCH 2/3] imx-atf: " Erik Larsson
2018-02-18 13:46 ` Baruch Siach
2018-02-18 13:55 ` Erik Larsson
2018-02-18 13:28 ` [Buildroot] [PATCH 3/3] add support for iMX8MQ-evk board Erik Larsson
2018-02-18 14:47 ` Baruch Siach
2018-02-19 6:01 ` Erik Larsson
2018-02-19 12:44 ` Baruch Siach
2018-02-19 10:12 ` Marcus Folkesson
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=20180219164406.GA22465@t450s.lan \
--to=gary.bisson@boundarydevices.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