Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] Rework support for the device tree
Date: Thu, 19 Jul 2012 09:42:03 +0200	[thread overview]
Message-ID: <20120719094203.493bd336@skate> (raw)
In-Reply-To: <5006E601.4080807@essensium.com>

Le Wed, 18 Jul 2012 18:36:17 +0200,
Arnout Vandecappelle <arnout.vandecappelle@essensium.com> a ?crit :

> > Do you really need to create the directory here? I would suspect that
> > all arches supporting the Device Tree already have their boot/dts/
> > directory, no?
> 
>   Nope.  For instance in 3.0 there was preliminary DTS support for ARM,
> but no arch/arm/boot/dts directory.  That said, I'm not entirely sure if the
> foo.dtb target would even work, because I don't see a rule for producing
> it for arm in 3.0...

Realistically, the ARM DT support was so limited (in number of
platforms supported) in 3.0 that I don't think it's worth the effort. I
think we can safely assume that for all practical cases,
arch/<ARCH>/boot/dts exists.

> > Hum, here when I do a make foobar.dtb, the foobar.dtb file ends up in
> > the main kernel source tree, not in arch/arm/boot/.
>   That's strange... For which architecture and kernel version?

That's just complete crap from my side. I got confused by the big
command line I typically use to build the kernel and concatenate the
DTB. The DTB indeed ends up in arch/arm/boot and Maxime's code is
correct in that respect.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2012-07-19  7:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 10:01 [Buildroot] [PATCHv2] Add some support for device tree kernels with appended trees Maxime Ripard
2012-07-03 10:01 ` [Buildroot] [PATCH 1/4] Rework support for the device tree Maxime Ripard
2012-07-15 12:34   ` Arnout Vandecappelle
2012-07-15 12:41     ` Arnout Vandecappelle
2012-07-16 12:57   ` Thomas Petazzoni
     [not found]     ` <5006E601.4080807@essensium.com>
2012-07-19  7:42       ` Thomas Petazzoni [this message]
2012-07-03 10:01 ` [Buildroot] [PATCH 2/4] Add support for appended device tree blobs for arm Maxime Ripard
2012-07-15 12:41   ` Arnout Vandecappelle
2012-07-16 13:01   ` Thomas Petazzoni
2012-07-16 13:10   ` Thomas Petazzoni
2012-07-03 10:01 ` [Buildroot] [PATCH 3/4] Factorise the u-boot images code Maxime Ripard
2012-07-15 12:42   ` Arnout Vandecappelle
2012-07-16 13:03   ` Thomas Petazzoni
2012-07-03 10:01 ` [Buildroot] [PATCH 4/4] Add cuImage(powerpc) and simpleImage(microblaze) as Linux kernel images variants Maxime Ripard
2012-07-15 12:43   ` Arnout Vandecappelle
2012-07-16 12:46 ` [Buildroot] [PATCHv2] Add some support for device tree kernels with appended trees Thomas Petazzoni

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=20120719094203.493bd336@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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