All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: Werner Grift <sky.captin@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH 73/73] Added absolute paths to checks when copying the device tree
Date: Tue, 17 Feb 2015 14:18:54 -0200	[thread overview]
Message-ID: <CAP9ODKqJa5vL1pThC6NzBLku2e5vn0VrvB=UPDn6bVnZv2a5gw@mail.gmail.com> (raw)
In-Reply-To: <CABmcM98cWC5b3pr-J3rW3zjDBsp9M3+F65BsVXbmjyDuPKrNxQ@mail.gmail.com>

On Tue, Feb 17, 2015 at 1:09 PM, Werner Grift <sky.captin@gmail.com> wrote:
> The device tree issue I refer too is the device tree file that is not being
> copied to the boot partition because the generated script
> create_image.sdcard contains if statements that assume that the current
> working directory is ${DEPLOY_DIR_IMAGE} which it is not. In my case it was
> ${OE_BASE} which makes sense since it is where bitbake is called from.

How is your platform setup?

FSL Community BSP usually looks like:

.
├── build
│   └── conf
├── README
├── setup-environment
└── sources
    ├── base
    ├── Documentation
    ├── meta-fsl-arm
    ├── meta-fsl-arm-extra
    ├── meta-fsl-demos
    ├── meta-openembedded
    └── poky

Is yours same layout?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  reply	other threads:[~2015-02-17 16:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11  9:19 [meta-fsl-arm][PATCH 73/73] Added absolute paths to checks when copying the device tree Werner Grift
2015-02-13  0:37 ` Otavio Salvador
2015-02-17  7:45   ` Werner Grift
2015-02-17  7:47     ` Werner Grift
2015-02-17 13:08     ` Otavio Salvador
2015-02-17 15:09       ` Werner Grift
2015-02-17 16:18         ` Otavio Salvador [this message]
2015-02-17 17:30           ` Werner Grift
2015-02-17 17:34             ` Otavio Salvador

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='CAP9ODKqJa5vL1pThC6NzBLku2e5vn0VrvB=UPDn6bVnZv2a5gw@mail.gmail.com' \
    --to=otavio@ossystems.com.br \
    --cc=meta-freescale@yoctoproject.org \
    --cc=sky.captin@gmail.com \
    /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.