From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/freescale-imx: Add option for all i.MX FW needs
Date: Thu, 25 Jun 2020 22:33:07 +0200 [thread overview]
Message-ID: <20200625203307.GP20645@scaer> (raw)
In-Reply-To: <DB8PR04MB5755C99B335ACE9AFC7552CDA7920@DB8PR04MB5755.eurprd04.prod.outlook.com>
Stephane, All,
On 2020-06-25 06:33 +0000, Stephane Viau (OSS) spake thusly:
> Thomas wrote:
> >However, I am wondering if package/freescale-imx/Config.in is the right
> >place for all this logic. After all, this is only related to the
> >firmware-imx package.
> >
> >Shouldn't we instead move that to
> >package/freescale-imx/firmware-imx/Config.in, with the following form:
> >
> >config BR2_PACKAGE_FREESCALE_IMX_NEEDS_DDR_FW
> > bool
> > default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8M
> > default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8MM
> > default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8MN
> >
> >and ditto the other options ? Here as well, it would require a
> >preparation patch to take care of the NEEDS_DDR_FW case, and then your
> >patch that handles all other FW files.
>
> I'd like to have Yann's and/or Gary's feedback on this. I'm using 'select' based on this comment:
> "
> As Yann mentioned on IRC:
> "Usually, when we introduce such option, it does not 'default y' based
> on some other options. Instead, the other options 'select' it."
> "
> from http://lists.busybox.net/pipermail/buildroot/2020-May/283180.html
True, that's what I said. That was based on the assumption that the
options would be in package/freescale-imx/Config.in.
But now, seeing the reasonning by Thomas, I agree with him: those are
better suited to live in package/freescale-imx/firmware-imx/Config.in/
And thus it is less clean that the variant selection in the generic
choice would have to catter with options specific to a package.
Hence, the "default y if ..." is indeed better.
Sorry I did not have that insight to begin with...
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-06-25 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 15:23 [Buildroot] [PATCH 0/2] package/freescale-imx: clean-up proposal Stephane Viau
2020-06-24 15:23 ` [Buildroot] [PATCH 1/2] package/freescale-imx: Add option for all i.MX FW needs Stephane Viau
2020-06-24 19:54 ` Fabio Estevam
2020-06-24 20:11 ` Fabio Estevam
2020-06-24 20:26 ` Yann E. MORIN
2020-06-24 20:58 ` Thomas Petazzoni
2020-06-25 6:33 ` Stephane Viau
2020-06-25 20:33 ` Yann E. MORIN [this message]
2020-06-29 6:38 ` Stephane Viau
2020-06-29 8:32 ` Kurt Van Dijck
2020-06-29 8:08 ` Gary Bisson
2020-06-29 8:26 ` Stephane Viau
2020-06-24 15:23 ` [Buildroot] [PATCH 2/2] package/freescale-imx/firmware-imx: Clean up the image/target semantic Stephane Viau
2020-06-24 19:57 ` Fabio Estevam
2020-06-24 21:04 ` Thomas Petazzoni
2020-06-24 19:22 ` [Buildroot] [PATCH 0/2] package/freescale-imx: clean-up proposal Yann E. MORIN
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=20200625203307.GP20645@scaer \
--to=yann.morin.1998@free.fr \
--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