All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Jardin <vjardin@free.fr>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: u-boot@lists.u-boot-project.org,
	Suraj Kakade <suraj.hanumantkakade@amd.com>,
	Markus Schneider-Pargmann <msp@baylibre.com>,
	Marek Vasut <marek.vasut+renesas@mailbox.org>,
	Denis Mukhin <dmukhin@ford.com>, Simon Glass <sjg@chromium.org>,
	Rasmus Villemoes <rv@rasmusvillemoes.dk>,
	Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v1 0/3] dts: build the DTS from a directory outside the tree
Date: Sun, 8 Nov 2026 18:49:47 +0100	[thread overview]
Message-ID: <avC2OzAeGxqVsJ2v@L30177.local> (raw)
In-Reply-To: <434743b6-17af-477d-a09f-d110d565f023@mailbox.org>

Hi,

> Upstream your hardware support and you won't need external DTs.

Even upstream, how does it solve the Yocto's and Buildroot's related
issues ? Both did try to workaround despite they are all upstream.

thank you,
  Vincent

  reply	other threads:[~2026-11-08 17:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08 15:50 [PATCH v1 0/3] dts: build the DTS from a directory outside the tree Vincent Jardin
2026-11-08 15:50 ` [PATCH v1 1/3] scripts: Makefile.dts: build the device tree with DEVICE_TREE= too Vincent Jardin
2026-11-08 15:50 ` [PATCH v1 2/3] scripts: Makefile.lib: add check of -u-boot.dtsi in the device tree source Vincent Jardin
2026-11-08 15:50 ` [PATCH v1 3/3] dts: build the device tree from a directory outside the tree, EXT_DTS_DIR Vincent Jardin
2026-11-08 16:31 ` [PATCH v1 0/3] dts: build the DTS from a directory outside the tree Marek Vasut
2026-11-08 17:49   ` Vincent Jardin [this message]
2026-11-08 18:00     ` Marek Vasut
2026-11-08 20:50       ` Vincent Jardin
2026-11-08 22:53         ` Marek Vasut
2026-11-09  0:58         ` E Shattow
2026-11-09 17:21           ` Vincent Jardin
2026-11-09 19:13             ` Tom Rini
2026-11-10  8:03               ` Vincent Jardin

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=avC2OzAeGxqVsJ2v@L30177.local \
    --to=vjardin@free.fr \
    --cc=dmukhin@ford.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=marek.vasut@mailbox.org \
    --cc=msp@baylibre.com \
    --cc=rv@rasmusvillemoes.dk \
    --cc=sjg@chromium.org \
    --cc=suraj.hanumantkakade@amd.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    /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.