From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Bajjuri Praneeth <praneeth@ti.com>, Julien Olivain <ju.o@free.fr>,
Lothar Felten <lothar.felten@gmail.com>,
buildroot@buildroot.org,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH v3 2/5] configs/beaglebone: Bump to Linux mainline 6.18.1
Date: Tue, 16 Dec 2025 16:40:43 +0100 [thread overview]
Message-ID: <20251216164043.458d92bb@windsurf> (raw)
In-Reply-To: <20251216151449.395253-3-kory.maincent@bootlin.com>
Hello Kory,
On Tue, 16 Dec 2025 15:14:42 +0000
Kory Maincent <kory.maincent@bootlin.com> wrote:
> board/beagleboard/beaglebone/linux.config | 682 ++++++++++++++++++
If you provide a custom defconfig, it really needs to be tailored to the platform.
> +CONFIG_ARCH_SUNPLUS=y
Why?
> +CONFIG_ARCH_KEYSTONE=y
Why?
> +CONFIG_ARCH_OMAP3=y
> +CONFIG_ARCH_OMAP4=y
Why?
> +CONFIG_SOC_OMAP5=y
Why?
> +CONFIG_SOC_AM33XX=y
> +CONFIG_SOC_AM43XX=y
Why?
> +CONFIG_SOC_DRA7XX=y
Why?
> +CONFIG_NET_DSA_TAG_RZN1_A5PSW=m
Useless.
> +CONFIG_HSR=m
Needed?
> +CONFIG_QRTR=m
> +CONFIG_QRTR_SMD=m
Same?
> +CONFIG_CAN=y
> +CONFIG_BT=m
Do we have BT?
> +CONFIG_BT_HCIUART=m
> +CONFIG_BT_HCIUART_BCM=y
> +CONFIG_BT_MRVL=m
> +CONFIG_BT_MRVL_SDIO=m
> +CONFIG_CFG80211=m
> +CONFIG_MAC80211=m
Do we have WiFi ?
> +CONFIG_RFKILL=y
> +CONFIG_RFKILL_INPUT=y
> +CONFIG_RFKILL_GPIO=y
> +CONFIG_NFC=m
Do we have NFC ?
> +CONFIG_VEXPRESS_CONFIG=y
Vexpress ?
> +CONFIG_ARM_SCMI_PROTOCOL=y
I don't think we're using SCMI.
> +CONFIG_IMX_SCMI_BBM_EXT=y
Not needed.
> +CONFIG_TI_SCI_PROTOCOL=y
Needed?
> +CONFIG_TRUSTED_FOUNDATIONS=y
> +CONFIG_EFI_CAPSULE_LOADER=m
> +CONFIG_MTD=y
> +CONFIG_MTD_TESTS=m
> +CONFIG_MTD_CMDLINE_PARTS=y
> +CONFIG_MTD_BLOCK=y
> +CONFIG_MTD_CFI=y
> +CONFIG_MTD_CFI_INTELEXT=y
> +CONFIG_MTD_PHYSMAP=y
> +CONFIG_MTD_PHYSMAP_OF=y
> +CONFIG_MTD_RAW_NAND=y
> +CONFIG_MTD_NAND_DENALI_DT=y
> +CONFIG_MTD_NAND_OMAP2=y
> +CONFIG_MTD_NAND_OMAP_BCH=y
> +CONFIG_MTD_NAND_BRCMNAND=y
Broadcom NAND driver ?
> +CONFIG_MTD_NAND_BRCMNAND_BCMBCA=y
> +CONFIG_MTD_NAND_BRCMNAND_BRCMSTB=y
> +CONFIG_MTD_NAND_BRCMNAND_IPROC=y
> +CONFIG_MTD_NAND_DAVINCI=y
Needed ?
> +CONFIG_MTD_SPI_NOR=y
> +CONFIG_MTD_UBI=y
> +CONFIG_BLK_DEV_LOOP=y
> +CONFIG_BLK_DEV_RAM=y
> +CONFIG_BLK_DEV_RAM_SIZE=65536
> +CONFIG_VIRTIO_BLK=y
> +CONFIG_AD525X_DPOT=y
> +CONFIG_AD525X_DPOT_I2C=y
Needed ?
> +CONFIG_ICS932S401=y
Needed ?
> +CONFIG_APDS9802ALS=y
etc. Please review the options :-)
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-12-16 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 15:14 [Buildroot] [PATCH 0/5] Add support for BeagleBone Green Eco board Kory Maincent via buildroot
2025-12-16 15:14 ` [Buildroot] [PATCH v3 1/5] configs/beaglebone: Switch to Bootlin glibc stable toolchain Kory Maincent via buildroot
2025-12-30 21:45 ` Julien Olivain via buildroot
2025-12-16 15:14 ` [Buildroot] [PATCH v3 2/5] configs/beaglebone: Bump to Linux mainline 6.18.1 Kory Maincent via buildroot
2025-12-16 15:40 ` Thomas Petazzoni via buildroot [this message]
2025-12-16 16:16 ` Kory Maincent via buildroot
2025-12-16 15:14 ` [Buildroot] [PATCH v3 3/5] board/beaglebone: Add BeagleBone Green Eco support Kory Maincent via buildroot
2025-12-18 12:13 ` Mohammed Sadik Shaik via buildroot
2025-12-16 15:14 ` [Buildroot] [PATCH v3 4/5] package/am33x-cm3: Switch to TI repo and bump to v0x192 Kory Maincent via buildroot
2025-12-16 15:14 ` [Buildroot] [PATCH v3 5/5] configs/beaglebone: Enable AM33X_CM3 config Kory Maincent via buildroot
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=20251216164043.458d92bb@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=ju.o@free.fr \
--cc=kory.maincent@bootlin.com \
--cc=lothar.felten@gmail.com \
--cc=praneeth@ti.com \
--cc=thomas.petazzoni@bootlin.com \
/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