All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fiona Klute via buildroot <buildroot@buildroot.org>
To: buildroot@cairnwater.com, Buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Adding Device Tree Overlays for MIPI-CSI2 Camera and libcamera to a buildroot Build
Date: Wed, 7 May 2025 18:41:04 +0200	[thread overview]
Message-ID: <b1d889ab-e5ce-4ff5-aaef-210e10c2c1cf@gmx.de> (raw)
In-Reply-To: <ddbed9a95b8f787377152092229828fd@cairnwater.com>

Hi Will!

Am 07.05.25 um 17:41 schrieb buildroot@cairnwater.com:
> Does anyone have any advice on how to add DTOs needed by libcamera to a 
> buildroot build?
> 
> We'd like to add Kieran's DTOs
> 
> https://git.uk.ideasonboard.com/camera/dt-overlays/src/branch/main/arch/ 
> arm64/boot/dts/freescale
> 
> to the buildroot default configuration for Debix Model A SBC
> 
> https://github.com/buildroot/buildroot/blob/master/configs/ 
> polyhex_debix_model_a_defconfig
> 
> Ideally we'd also like to add the overlays for the Sony IMX 708 Image 
> Sensor used in the RPi V3 camera but these aren't mainline:
> 
> https://github.com/raspberrypi/linux/blob/rpi-6.12.y/arch/arm/boot/dts/ 
> overlays/imx708-overlay.dts
> https://github.com/raspberrypi/linux/blob/rpi-6.12.y/arch/arm/boot/dts/ 
> overlays/imx708.dtsi

You can use BR2_LINUX_KERNEL_CUSTOM_DTS_DIR for that: Just place the 
DTSOs in the configured directory (with appropriate structure), and 
Buildroot will build them automatically. DTBOs will be in 
${OUTPUT_DIR}/images. From there you'll need to adjust the boot process 
for your board to actually apply the overlay. If you want to send a 
patch, the BR2_LINUX_KERNEL_CUSTOM_DTS_DIR should be inside the board 
directory.

With RPi overlays you'll probably have to adjust the overlays a bit so 
referenced names fit, etc. You're using a different board, and I've seen 
cases where DTS for RPi boards from mainline and RPi kernels use 
different names. But that doesn't change the build process. :-)

Best regards,
Fiona

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-05-07 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 15:41 [Buildroot] Adding Device Tree Overlays for MIPI-CSI2 Camera and libcamera to a buildroot Build buildroot
2025-05-07 16:41 ` Fiona Klute via buildroot [this message]
2025-05-07 18:31   ` buildroot
2025-05-07 20:06     ` Fiona Klute via buildroot
2025-05-08  7:46       ` buildroot
2025-05-14 17:36         ` buildroot
2025-05-14 18:59           ` Edgar Bonet via buildroot
2025-05-15 16:11             ` buildroot
2025-05-21 17:17               ` Fiona Klute via buildroot
2025-05-21 17:26           ` Fiona Klute 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=b1d889ab-e5ce-4ff5-aaef-210e10c2c1cf@gmx.de \
    --to=buildroot@buildroot.org \
    --cc=buildroot@cairnwater.com \
    --cc=fiona.klute@gmx.de \
    /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.