From: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
To: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Devicetree Discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: [PATCH] dtc: Add -i option to support search paths
Date: Mon, 12 Mar 2012 08:54:34 -0500 [thread overview]
Message-ID: <E1S75hq-0005Wi-Jb@jdl.com> (raw)
In-Reply-To: <1331082612-10612-1-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
> It is often inconvenient to place device tree files in the same directory
> as their includes, or to specify the full path to include files.
>
> An example of this is in U-Boot where we have a .dtsi file for each SOC
> type, and this is included by the board .dts file. We need to either use
> a mechanism like:
>
> /include/ ARCH_CPU_DTS
>
> with sed or cpp to perform the replacement with the correct path, or
> we must specify the full path in the file:
>
> /include/ "../../arch/arm/dts/tegra20.dtsi"
>
> The first option is not desirable since it requires anyone compiling the
> file to first pre-process it. The second is not desirable since it
> introduces a path which is project-specific into a file which is supposed
> to be a hardware description. For example Linux and U-Boot are unlikely to
> put these include files in the same place.
>
> It is much more convenient to specify the search patch on the command line
> as is done with C pre-processors, for example.
>
> Introduce a -i option to add to the list of search paths used to find
> source and include files.
>
> We cannot use -I as it is already in use. Other suggestions welcome.
>
> Signed-off-by: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Any comments here? I'm inclined to aply it as is.
Thanks,
jdl
next prev parent reply other threads:[~2012-03-12 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 1:10 [PATCH] dtc: Add -i option to support search paths Simon Glass
[not found] ` <1331082612-10612-1-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2012-03-12 13:54 ` Jon Loeliger [this message]
[not found] ` <E1S75hq-0005Wi-Jb-CYoMK+44s/E@public.gmane.org>
2012-03-12 17:13 ` Simon Glass
2012-03-12 23:53 ` David Gibson
[not found] ` <20120312235332.GD24916-MK4v0fQdeXQXU02nzanrWNbf9cGiqdzd@public.gmane.org>
2012-03-14 16:16 ` Simon Glass
2012-03-15 3:04 ` [PATCH v2] " Simon Glass
[not found] ` <1331780653-13750-1-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2012-03-18 15:53 ` Jon Loeliger
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=E1S75hq-0005Wi-Jb@jdl.com \
--to=jdl-cyomk+44s/e@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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.