All of lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Custom DTS declaration
@ 2024-04-14  7:40 Christopher Hunt
  2024-04-28 17:23 ` Arnout Vandecappelle via buildroot
  0 siblings, 1 reply; 3+ messages in thread
From: Christopher Hunt @ 2024-04-14  7:40 UTC (permalink / raw)
  To: buildroot


[-- Attachment #1.1: Type: text/plain, Size: 946 bytes --]

Hi there,

I’m somewhat confused about the device-tree that I can view from the Linux CLI vs what I’m supplying to buildroot.

If I look at /proc/device-tree/model then I see "Microchip SAMA5D27 WLSOM1 EK”. However, my board/cuprous/gw/linux/dts/at91-sama5d27_wlsom1_cuprous_gw.dts declares, "Microchip SAMA5D27 WLSOM1 Cuprous Gateway”. I’m declaring the use of that DTS via configs/microchip_sama5d27_wlsom1_cuprous_gw_defconfig with:

	BR2_LINUX_KERNEL_INTREE_DTS_NAME="at91-sama5d27_wlsom1_cuprous_gw”
	BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="board/cuprous/gw/linux/dts/at91-sama5d27_wlsom1_cuprous_gw.dts"

Uboot is configured to use its own DTS with the name of "Microchip SAMA5D27 WLSOM1 EK”, so it could be that, or it could just be that I’ve not declared my custom Linux DTS correctly.

Anything obvious?

Full repo here: https://github.com/cuprous-au/buildroot/tree/2022.05.x

Thanks for any help.

Cheers,
-C

[-- Attachment #1.2: Type: text/html, Size: 1866 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Buildroot] Custom DTS declaration
  2024-04-14  7:40 [Buildroot] Custom DTS declaration Christopher Hunt
@ 2024-04-28 17:23 ` Arnout Vandecappelle via buildroot
  2024-04-29 23:28   ` Christopher Hunt
  0 siblings, 1 reply; 3+ messages in thread
From: Arnout Vandecappelle via buildroot @ 2024-04-28 17:23 UTC (permalink / raw)
  To: Christopher Hunt, buildroot



On 14/04/2024 09:40, Christopher Hunt wrote:
> Hi there,
> 
> I’m somewhat confused about the device-tree that I can view from the Linux CLI 
> vs what I’m supplying to buildroot.
> 
> If I look at /proc/device-tree/model then I see "Microchip SAMA5D27 WLSOM1 EK”. 
> However, my board/cuprous/gw/linux/dts/at91-sama5d27_wlsom1_cuprous_gw.dts 
> declares, "Microchip SAMA5D27 WLSOM1 Cuprous Gateway”. I’m declaring the use of 
> that DTS via configs/microchip_sama5d27_wlsom1_cuprous_gw_defconfig with:
> 
> BR2_LINUX_KERNEL_INTREE_DTS_NAME="at91-sama5d27_wlsom1_cuprous_gw”
> BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="board/cuprous/gw/linux/dts/at91-sama5d27_wlsom1_cuprous_gw.dts"

  When specified like this, you will build 2 versions of the DTB:
- one from the kernel sources, arch/arm/boot/dts/sama5d27_wlsom1_cuprous_gw.dts
- one from the Buildroot source,
   board/cuprous/gw/linux/dts/at91-sama5d27_wlsom1_cuprous_gw.dts

They don't have the same basename, so you'll get two DTBs in output/images. My 
guess is that you booted with sama5d27_wlsom1_cuprous_gw..dtb rather than
at91-sama5d27_wlsom1_cuprous_gw.dtb

  Regards,
  Arnout

> 
> Uboot is configured to use its own DTS with the name of "Microchip SAMA5D27 
> WLSOM1 EK”, so it could be that, or it could just be that I’ve not declared my 
> custom Linux DTS correctly.
> 
> Anything obvious?
> 
> Full repo here: https://github.com/cuprous-au/buildroot/tree/2022.05.x 
> <https://github.com/cuprous-au/buildroot/tree/2022.05.x>
> 
> Thanks for any help.
> 
> Cheers,
> -C
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Buildroot] Custom DTS declaration
  2024-04-28 17:23 ` Arnout Vandecappelle via buildroot
@ 2024-04-29 23:28   ` Christopher Hunt
  0 siblings, 0 replies; 3+ messages in thread
From: Christopher Hunt @ 2024-04-29 23:28 UTC (permalink / raw)
  To: Arnout Vandecappelle; +Cc: buildroot


[-- Attachment #1.1: Type: text/plain, Size: 498 bytes --]


> On 29 Apr 2024, at 3:23 AM, Arnout Vandecappelle <arnout@mind.be> wrote:
> 
> They don't have the same basename, so you'll get two DTBs in output/images. My guess is that you booted with sama5d27_wlsom1_cuprous_gw..dtb rather than
> at91-sama5d27_wlsom1_cuprous_gw.dtb


Thanks for the reply.

Shouldn’t U-Boot have its own DTS, and the kernel another? That was my expectation, although I am confused about the relationship of DTS files between U-Boot and the kernel.

Cheers,
-C

[-- Attachment #1.2: Type: text/html, Size: 2252 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-04-29 23:28 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-14  7:40 [Buildroot] Custom DTS declaration Christopher Hunt
2024-04-28 17:23 ` Arnout Vandecappelle via buildroot
2024-04-29 23:28   ` Christopher Hunt

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.