From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: Frieder Schrempf <frieder.schrempf@kontron.de>,
Michael Walle <michael@walle.cc>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org, Heiko Thiery <heiko.thiery@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v5] configs/kontron_bl_imx8mm_defconfig: new defconfig
Date: Mon, 31 Jan 2022 18:11:44 +0100 [thread overview]
Message-ID: <86bf975a-1599-005a-5ebc-a149cc973da4@benettiengineering.com> (raw)
In-Reply-To: <CAOf5uwmeT8WVUc3xvP0DjrVDLj9egvJz0+JEvWhgojnEVhyTyw@mail.gmail.com>
On 31/01/22 17:42, Michael Nazzareno Trimarchi wrote:
[SNIP]
>>>>> diff --git a/configs/kontron_bl_imx8mm_defconfig b/configs/kontron_bl_imx8mm_defconfig
>>>>> new file mode 100644
>>>>> index 0000000000..0cf0115bfa
>>>>> --- /dev/null
>>>>> +++ b/configs/kontron_bl_imx8mm_defconfig
>>>>> @@ -0,0 +1,58 @@
>>>>> +# Architecture
>>>>> +BR2_aarch64=y
>>>>> +BR2_ARM_FPU_VFPV3=y
>>>>> +
>>>>> +BR2_GLOBAL_PATCH_DIR="board/kontron/bl-imx8mm/patches"
>>>>> +
>>>>> +# System
>>>>> +BR2_TARGET_GENERIC_GETTY_PORT="ttymxc2"
>>>>> +
>>>>> +# Kernel
>>>>> +BR2_LINUX_KERNEL=y
>>>>> +BR2_LINUX_KERNEL_CUSTOM_VERSION=y
>>>>> +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.16"
>>>>> +BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y
>>>>> +BR2_LINUX_KERNEL_DTS_SUPPORT=y
>>>>> +BR2_LINUX_KERNEL_INTREE_DTS_NAME="freescale/imx8mm-kontron-n801x-s"
>>>>> +BR2_LINUX_KERNEL_DTB_KEEP_DIRNAME=y
>>>>> +BR2_LINUX_KERNEL_INSTALL_TARGET=y
>>>>> +BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
>>>>> +
>>>>> +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_16=y
>>>>> +
>>>>> +BR2_PACKAGE_FREESCALE_IMX=y
>>>>> +BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8MM=y
>>>>> +BR2_PACKAGE_FIRMWARE_IMX=y
>>>>> +
>>>>> +# Filesystem / image
>>>>> +BR2_TARGET_ROOTFS_EXT2=y
>>>>> +BR2_TARGET_ROOTFS_EXT2_4=y
>>>>> +BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
>>>>> +
>>>>> +# Bootloader
>>>>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
>>>>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION=y
>>>>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION_VALUE="v2.6"
>>>>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="imx8mm"
>>>>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y
>>>>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES="IMX_BOOT_UART_BASE=0x30880000"
>>>>> +BR2_TARGET_UBOOT=y
>>>>> +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
>>>>> +BR2_TARGET_UBOOT_CUSTOM_VERSION=y
>>>>> +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2022.01"
>>>>> +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="kontron-sl-mx8mm"
>>>>> +BR2_TARGET_UBOOT_NEEDS_DTC=y
>>>>> +BR2_TARGET_UBOOT_NEEDS_PYTHON3=y
>>>>> +BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y
>>>>> +BR2_TARGET_UBOOT_NEEDS_ATF_BL31=y
>>>>> +BR2_TARGET_UBOOT_NEEDS_ATF_BL31_BIN=y
>>>>> +BR2_TARGET_UBOOT_NEEDS_IMX_FIRMWARE=y
>>>>> +BR2_TARGET_UBOOT_FORMAT_CUSTOM=y
>>>>> +BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME="flash.bin"
>>>>> +BR2_TARGET_UBOOT_SPL=y
>>>>> +
>>>>> +# Required host tools to create the SD/eMMC image
>>>>> +BR2_ROOTFS_POST_BUILD_SCRIPT="board/kontron/bl-imx8mm/post-build.sh"
>>>>> +BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
>>>>> +BR2_ROOTFS_POST_SCRIPT_ARGS="-c $(BINARIES_DIR)/genimage.cfg"
>>>>> +BR2_PACKAGE_HOST_GENIMAGE=y
>>>>
>>>> I have seen that some people like to have this organization but it's
>>>> not really nice to maintain. I would like
>>>> to savedefconfig and use that one instead of having nice commented
>>>> part. Is this mandatory?
>>>
>>> As far as I know there is no rule how to do that. For me it seems to
>>> be more readable and clean. But this is only my opinion.
>>
>> As Heiko pointed it's a very good habit.
>>
>> One thing that must be taken into account while doing it, is to keep the
>> various BR2_* configs ordered as they are ordere inside the various
>> Config.in
>
> There are good information indeed but even those information must be
> keep updated. Daily work show me that work on
> savedefconfig make things nicely. Some of your option can be at some
> point autoselect by another one and so on.
Yes, you're right, I've noticed that too. It's "not that automatic", but
if you check the first 25 defconfigs you can see that more or less the
70% use the "descriptive" way. So basically one should savedefconfig to
another file and compare to the configs/*_defconfig and eventually modify.
Anyway there is still not a standard decided. So maintainers will accept
both ways.
Cheers
--
Giulio Benetti
Benetti Engineering sas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-31 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 15:30 [Buildroot] [PATCH v5] configs/kontron_bl_imx8mm_defconfig: new defconfig Heiko Thiery
2022-01-31 15:36 ` Michael Nazzareno Trimarchi
2022-01-31 15:42 ` Heiko Thiery
2022-01-31 16:38 ` Giulio Benetti
2022-01-31 16:42 ` Michael Nazzareno Trimarchi
2022-01-31 17:11 ` Giulio Benetti [this message]
2022-01-31 17:45 ` Bartosz Bilas
2022-02-01 7:22 ` Heiko Thiery
2022-02-01 20:51 ` Arnout Vandecappelle
2022-01-31 15:37 ` Giulio Benetti
2022-02-12 13:40 ` Arnout Vandecappelle
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=86bf975a-1599-005a-5ebc-a149cc973da4@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=buildroot@buildroot.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=heiko.thiery@gmail.com \
--cc=michael@amarulasolutions.com \
--cc=michael@walle.cc \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.