All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Galauner <andreas@galauner.de>
To: yocto@yoctoproject.org
Subject: linux-yocto custom device tree in overlay
Date: Wed, 07 May 2014 17:33:29 +0200	[thread overview]
Message-ID: <536A5249.9030907@galauner.de> (raw)

Hi Yocto Community,

I'm currently trying to build a custom image for a beaglebone black for
which I need to enable the can-controllers on the SoC. I managed to
create an overlay which already deals with building a few tools for CAN
communication, I created a kernel config snippet for linux-yocto to
enable CAN-support in the kernel and it already works with a USB
transceiver.

Now I need to modify the device tree for the board to enable the SoC
controllers. How do I put the device tree into my overlay? I tried
several ways, but the kernel buildsystem doesn't seem to find the dts
file to be compiled.

That definitely doesn't work:
> SRC_URI += "file://can.cfg \
>             file://am335x-boneblack-cansniff.dts"
> KERNEL_DEVICETREE = "am335x-boneblack-cansniff.dtb"

Any ideas? Google wasn't too fruitful either.
With non-yocto kernels I always put the device tree into the whole path
like 'git/arch/arm/boot/dts/mydevicetree.dts'  but that also doesn't
seem to work on linux-yocto because it uses another layout in its
working directory.

I'd rather not want to create my own git repo for linux-yocto like I did
for another project where I needed the same.

Thanks for your help,
- Andy


             reply	other threads:[~2014-05-07 15:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 15:33 Andreas Galauner [this message]
2014-05-07 19:37 ` linux-yocto custom device tree in overlay Bruce Ashfield
2014-05-08 13:48   ` Andreas Galauner
2014-05-08 15:17     ` Bruce Ashfield
2016-07-18 16:39       ` adnan

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=536A5249.9030907@galauner.de \
    --to=andreas@galauner.de \
    --cc=yocto@yoctoproject.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.