All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv4 0/6] Add some support for device tree kernels
Date: Mon, 30 Jul 2012 21:16:16 +0200	[thread overview]
Message-ID: <20120730211616.424941a8@skate> (raw)
In-Reply-To: <1343651569-6450-1-git-send-email-maxime.ripard@free-electrons.com>

Hello,

Le Mon, 30 Jul 2012 14:32:43 +0200,
Maxime Ripard <maxime.ripard@free-electrons.com> a ?crit :

> This is a refactoring of the previous basic device tree
> options available for microblaze.

I am fine with the general design, but it doesn't work: the
qemu_microblazeel_defconfig doesn't build.

I had to make some changes:

 *) Change the defconfig to limit the number of modifications compared
    to the previous versions (keep architecture, toolchain, etc.)
    properties.

 *) Create a special kconfig entry for the linux.bin image format
    (Microblaze specific). This format requires mkimage to generate
    linux.bin, so we need to select BR2_LINUX_KERNEL_UBOOT_IMAGE. It
    probably worked on your system because you have mkimage installed
    system-wide, but since it isn't part of our required dependencies,
    you shouldn't rely on it.

However, even with those fixes, building the DTB doesn't work.
Apparently, system.dts/system.dtb are kind of "reserved" names for
Microblaze (from a quick reading of arch/microblaze/boot/Makefile). I
have the following build error:

Kernel: arch/microblaze/boot/linux.bin is ready  (#1)
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  CALL    scripts/checksyscalls.sh
  Building modules, stage 2.
  MODPOST 0 modules
PATH="/home/test/outputs/t/host/bin:/home/test/outputs/t/host/usr/bin:/home/test/outputs/t/host/usr/sbin/:/usr/local/bin:/usr/bin:/bin:/usr/games" PERLLIB="/home/test/outputs/t/host/usr/lib/perl" /usr/bin/make -j2 HOSTCC="/usr/bin/gcc" HOSTCFLAGS="" ARCH=microblaze INSTALL_MOD_PATH=/home/test/outputs/t/target CROSS_COMPILE=" /home/test/outputs/t/host/usr/bin/microblazeel-unknown-linux-gnu-" DEPMOD=/home/test/outputs/t/host/usr/sbin/depmod -C /home/test/outputs/t/build/linux-3.3.7 system.dtb
make[2]: *** No rule to make target `system.dtb'.  Stop.
make[1]: *** [/home/test/outputs/t/build/linux-3.3.7/.stamp_built] Error 2
make: *** [all] Error 2

It would be good if you could fix this problem and resubmit. Please
base your new work using the following branch, which includes the two
changes I've mentioned above:

http://git.free-electrons.com/users/thomas-petazzoni/buildroot/log/?h=device-tree-support

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-30 19:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 12:32 [Buildroot] [PATCHv4 0/6] Add some support for device tree kernels Maxime Ripard
2012-07-30 12:32 ` [Buildroot] [PATCH 1/6] Revert "Microblaze: build kernel with device tree" Maxime Ripard
2012-07-30 12:32 ` [Buildroot] [PATCH 2/6] Rework support for the device tree Maxime Ripard
2012-07-30 12:32 ` [Buildroot] [PATCH 3/6] Factorize the u-boot images code Maxime Ripard
2012-07-30 12:32 ` [Buildroot] [PATCH 4/6] Add support for appended device tree blobs for arm Maxime Ripard
2012-07-30 12:32 ` [Buildroot] [PATCH 5/6] Add cuImage(powerpc) and simpleImage(microblaze) as Linux kernel images variants Maxime Ripard
2012-07-30 12:32 ` [Buildroot] [PATCH 6/6] Update s6lx9 microblaze default configuration Maxime Ripard
2012-07-30 13:55 ` [Buildroot] [PATCH 1/2] Update qemu microblazeel " Maxime Ripard
2012-07-30 13:55   ` [Buildroot] [PATCH 2/2] Update qemu microblazebe " Maxime Ripard
2012-07-30 19:16 ` Thomas Petazzoni [this message]
2012-07-31 10:13   ` [Buildroot] [PATCHv4 0/6] Add some support for device tree kernels Maxime Ripard
2012-07-31 21:44 ` 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=20120730211616.424941a8@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 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.