Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Stefan Christ <s.christ@phytec.de>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/7] linux-dtb.inc: fix detection of ending '.dts'
Date: Mon, 19 Oct 2015 11:21:10 +0200	[thread overview]
Message-ID: <20151019092110.GE3869@lws-christ> (raw)
In-Reply-To: <CAP71Wjzhq_UVTb0cZHWLs=FPp0YRseXb-Q0RyAQXjDAuKFFLuQ@mail.gmail.com>

Hi,

On Mon, Oct 19, 2015 at 11:05:58AM +0200, Nicolas Dechesne wrote:
> On Mon, Oct 19, 2015 at 11:03 AM, Stefan Christ <s.christ@phytec.de> wrote:
> > Hmm, the meaning of the code seems to be non obvious. I just looked at sed
> > replacement and concluded that it's about the file name ending.
> >
> > Using the full path to the dtb file is not supported by the code anyway, e.g.
> >
> >    DTB_PATH="${B}/arch/${ARCH}/boot/dts/${DTB}"
> >
> > would be wrong.
> >
> > So the correct solution would check both cases
> >
> >    - full path or only filename and
> >    - ending is dts or dtb
> >
> > Correct?
> 
> 
> If you look at the commit that introduced this code, e.g. 72980d5b,
> you can see that this code was added to support the 'legacy' case
> which was the absolute path of the .dts file, or the new case which is
> the .dtb file name. e.g.:
> 
> ==
>     ,----[ Original definition ]
>     | KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx6q-sabresd.dts"
>     `----
> 
>     Becomes:
> 
>     ,----[ New definition ]
>     | KERNEL_DEVICETREE = "imx6q-sabresd.dtb"
>     `----
> ==
> 
> so the '/dts/' was used to detect the legacy case, and print a warning
> in that condition.
> 

Yeah. Your right. The code is correct. The line

    DTB=`basename ${DTB} | sed 's,\.dts$,.dtb,g'`

will strip off the directories and replaces the ending. I overlooked that
somehow.  So drop my 'fixes', please.

What about my rework patches? I will resend them if they are ok.

Mit freundlichen Grüßen / Kind regards,
	Stefan Christ


  reply	other threads:[~2015-10-19  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19  8:15 [PATCH 0/7] Two fixes and some changes for linux-dtb.inc Stefan Christ
2015-10-19  8:15 ` [PATCH 1/7] linux-dtb.inc: fix detection of ending '.dts' Stefan Christ
2015-10-19  8:27   ` Nicolas Dechesne
2015-10-19  9:03     ` Stefan Christ
2015-10-19  9:05       ` Nicolas Dechesne
2015-10-19  9:21         ` Stefan Christ [this message]
2015-10-19  9:46           ` Nicolas Dechesne
2015-10-23 21:17             ` Burton, Ross
2015-10-26  8:18               ` Stefan Christ
2015-10-19  8:15 ` [PATCH 2/7] linux-dtb.inc: fix file ending detection Stefan Christ
2015-10-19  8:15 ` [PATCH 3/7] linux-dtb.inc: remove unneeded 'cd' Stefan Christ
2015-10-19  8:15 ` [PATCH 4/7] linux-dtb.inc: use same variable name DTB for all elements of KERNEL_DEVICETREE Stefan Christ
2015-10-19  8:15 ` [PATCH 5/7] linux-dtb.inc: explicit test for empty string not needed Stefan Christ
2015-10-19  8:15 ` [PATCH 6/7] linux-dtb.inc: refactor common code to function normalize_dtb Stefan Christ
2015-10-19  8:15 ` [PATCH 7/7] linux-dtb.inc: refactor common code to function get_real_dtb_path_in_kernel Stefan Christ

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=20151019092110.GE3869@lws-christ \
    --to=s.christ@phytec.de \
    --cc=nicolas.dechesne@linaro.org \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox