From: Lucas Stach <l.stach@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Subject: Re: [ptxdist] Multiple device trees
Date: Wed, 15 Jun 2016 15:15:21 +0200 [thread overview]
Message-ID: <1465996521.14866.1.camel@pengutronix.de> (raw)
In-Reply-To: <CABDcavYLHkBq=++eYT85A_W29Vm8zPFwpo=0PPPnf6o3-LiaDQ@mail.gmail.com>
Am Mittwoch, den 15.06.2016, 14:41 +0200 schrieb Guillermo Rodriguez
Garcia:
> Hello all,
>
> Is it possible to configure ptxdist to compile multiple device trees
> as part of the same BSP/project/platformconfig? This is to support a
> scenario where there are two versions of the target hardware, with
> slight differences in the hardware (gpios, IRQs).
>
Yes. PTXCONF_DTC_OFTREE_DTS is a simple space separated list of DTs to
compile.
Regards,
Lucas
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-06-15 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 12:41 Guillermo Rodriguez Garcia
2016-06-15 13:15 ` Lucas Stach [this message]
2016-06-15 17:07 ` Guillermo Rodriguez Garcia
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=1465996521.14866.1.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox