From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [EXT] Re: [PATCH v4 1/9] package/nxp: new package directory
Date: Thu, 6 Feb 2020 10:51:50 +0100 [thread overview]
Message-ID: <20200206105150.14fb9a83@windsurf> (raw)
In-Reply-To: <CA+h21hqTB3LVV91DaRf=b=XyUv_UhQB0Snjv-qCu2+z+RW+k=g@mail.gmail.com>
On Thu, 6 Feb 2020 11:44:24 +0200
Vladimir Oltean <olteanv@gmail.com> wrote:
> > > This seems to be a duplication of the FREESCALE_IMX_EXTRACT_HELPER, isn't
> > > it?
> > > Do we then can remove the other one and use only the new "nxp" one?
> > >
> > > By the way is there a plan to move all NXP specific packages (qoriq and imx) to
> > > the nxp subdir?
> > Yes, the helper is the duplication of FREESCALE_IMX_EXTRACT_HELPER.
> > Because Freescale is merged into NXP a few years ago, according to NXP's policy, we need to use nxp, instead of freescale.
> > So, I think the packages related NXP should be move into nxp directory.
> >
>
> Is it really NXP policy though?
> The thing is that LS1028A and several other boards are already
> supported by some downstream Buildroot patches, so it makes sense to
> keep using the folder names that we have there, i.e. "nxp" instead of
> changing to "freescale".
The proposal is not to change from nxp to freescale, but the opposite.
However, I think it's good to keep in mind that NXP's policy applies to
whatever NXP does. The Buildroot project is independent and is not
forced in any way to comply with NXP policies.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-06 9:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 10:52 [Buildroot] [PATCH v4 1/9] package/nxp: new package directory Changming Huang
2020-02-05 10:52 ` [Buildroot] v4 [PATCH 2/9] package/qoriq-rcw: move rcw into nxp and rename it Changming Huang
2020-02-05 10:52 ` [Buildroot] [PATCH v4 3/9] package/qoriq-rcw: bump to version LSDK-19.09 Changming Huang
2020-02-05 10:52 ` [Buildroot] [PATCH v4 4/9] package/qoriq-rcw: add target rcw binary support Changming Huang
2020-02-05 10:52 ` [Buildroot] [PATCH v4 5/9] boot/arm-trusted-firmware: introduce two new options Changming Huang
2020-02-05 12:29 ` Thomas Petazzoni
2020-02-07 1:21 ` [Buildroot] [EXT] " Jerry Huang
2020-02-05 10:52 ` [Buildroot] [PATCH v4 6/9] package/qoriq-cadence-dp-firmware: new package Changming Huang
2020-02-05 13:47 ` Michael Walle
2020-02-07 1:26 ` [Buildroot] [EXT] " Jerry Huang
2020-02-07 8:52 ` Michael Walle
2020-02-05 10:52 ` [Buildroot] [PATCH v4 7/9] package/qoriq-rcw:Enable IIC5_PMUX and CLK_OUT_PMUX for GPIO Changming Huang
2020-02-05 10:52 ` [Buildroot] [PATCH v4 8/9] package/nxp/qoriq-rcw: introduce BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE for boot mode Changming Huang
2020-02-06 9:50 ` Sergey Matyukevich
2020-02-05 10:52 ` [Buildroot] [PATCH v4 9/9] board/nxp/ls1028ardb: new board Changming Huang
2020-02-05 12:39 ` Vladimir Oltean
2020-02-07 5:23 ` [Buildroot] [EXT] " Jerry Huang
2020-02-05 14:08 ` [Buildroot] [PATCH v4 1/9] package/nxp: new package directory Heiko Thiery
2020-02-06 3:41 ` [Buildroot] [EXT] " Jerry Huang
2020-02-06 9:44 ` Vladimir Oltean
2020-02-06 9:51 ` Thomas Petazzoni [this message]
2020-02-06 10:04 ` Vladimir Oltean
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=20200206105150.14fb9a83@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox