From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3 0/6] Add some support for device tree kernels
Date: Mon, 30 Jul 2012 11:38:07 +0200 [thread overview]
Message-ID: <501655FF.1040501@free-electrons.com> (raw)
In-Reply-To: <CAHkwnC-uYDO_V1_oWZG2dmwgypdk6AOMmBjq3DsaXp=3n+7iLA@mail.gmail.com>
Le 30/07/2012 10:33, Fabio Porcedda a ?crit :
> On Fri, Jul 27, 2012 at 8:59 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
>> Le 27/07/2012 18:06, Fabio Porcedda a ?crit :
>>> thanks for the work, this feature it's very useful for me,
>>> i tried your patches and i tried to build a kernel for arm, but it
>>> failed to build it,
>>> this is the tail of the output log:
>>>
>>> cat /home/fabiopo/porting-pro3/ge863-pro3-linux-3.6/buildroot-dt/output/build/linux-3.5/arch/arm/boot/zImage
>>> /home/fabiopo/porting-pro3/ge863-pro3-linux-3.6/buildroot-dt/output/build/linux-3.5/arch/arm/boot/"usb_a9260".dtb
>>>> /home/fabiopo/porting-pro3/ge863-pro3-linux-3.6/buildroot-dt/output/build/linux-3.5/arch/arm/boot/zImage_dtb
>>> mv /home/fabiopo/porting-pro3/ge863-pro3-linux-3.6/buildroot-dt/output/build/linux-3.5/arch/arm/boot/zImage_dtb
>>> /home/fabiopo/porting-pro3/ge863-pro3-linux-3.6/buildroot-dt/output/build/linux-3.5/arch/arm/boot/zImage
>>> # We need to generate a new u-boot image that takes into
>>> # account the extra-size added by the device tree at the end
>>> # of the image. To do so, we first need to retrieve both load
>>> # address and entry point for the kernel from the already
>>> # generate uboot image before using mkimage -l.
>>> LOAD=` -l /home/fabiopo/porting-pro3/ge863-pro3-linux-3.6/buildroot-dt/output/build/linux-3.5/arch/arm/boot/uImage
>>> | sed -n 's/Load Address: \([0-9]*\)/\1/p'`; ENTRY=` -l
>>> /home/fabiopo/porting-pro3/ge863-pro3-linux-3.6/buildroot-dt/output/build/linux-3.5/arch/arm/boot/uImage
>>> | sed -n 's/Entry Point: \([0-9]*\)/\1/p'`; -A arm -O linux -T kernel
>>> -C none -a ${LOAD} -e ${ENTRY} -n 'Linux Buildroot' -d
>>> /home/fabiopo/porting-pro3/ge863-pro3-linux-3.6/buildroot-dt/output/build/linux-3.5/arch/arm/boot/zImage
>>> /home/fabiopo/porting-pro3/ge863-pro3-linux-3.6/buildroot-dt/output/build/linux-3.5/arch/arm/boot/uImage
>>> /bin/bash: -l: command not found
>>> /bin/bash: -l: command not found
>>> /bin/bash: -A: command not found
>>> make: *** [/home/fabiopo/porting-pro3/ge863-pro3-linux-3.6/buildroot-dt/output/build/linux-3.5/.stamp_built]
>>> Error 127
>>>
>>>
>>> I've applied your patches on top of the commit
>>> fd08153b9d677d654add6c580b9ccc5c27d672e2,
>>>
>>> My defconfig is:
>>> BR2_arm=y
>>> BR2_arm926t=y
>>> BR2_TOOLCHAIN_EXTERNAL=y
>>> BR2_LINUX_KERNEL=y
>>> BR2_LINUX_KERNEL_CUSTOM_VERSION=y
>>> BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.5"
>>> BR2_LINUX_KERNEL_DEFCONFIG="at91_dt"
>>> BR2_LINUX_KERNEL_INTREE_DTS_NAME="usb_a9260"
>>> BR2_LINUX_KERNEL_APPENDED_UIMAGE=y
>>
>> I have seen no such bugs during my testing, but can you try with the
>> attached patch?
>
> The problem it's on the patch "[PATCH 2/4] Add support for appended
> device tree blobs for arm ",
> please read my replay on the patch.
>
>> I've only discovered this simplification of the code recently and didn't
>> take the time to submit a patch for it, I guess I have the opportunity
>> now :)
>
> I tried your patch on top of the others, but the patch doesn't apply:
>
> git apply < ~/Downloads/uimage-dtb.patch
> <stdin>:20: trailing whitespace.
> cat $(KERNEL_ARCH_PATH)/boot/$(KERNEL_DTS_NAME).dtb >>
> $(KERNEL_ARCH_PATH)/boot/zImage
> <stdin>:21: trailing whitespace.
> # We need to generate the uImage here after that so that the uImage is
> <stdin>:22: trailing whitespace.
> # generated with the right image size.
> <stdin>:23: trailing whitespace.
> $(TARGET_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(@D) uImage
> <stdin>:29: trailing whitespace.
> cat $(KERNEL_ARCH_PATH)/boot/$(KERNEL_DTS_NAME).dtb >>
> $(KERNEL_ARCH_PATH)/boot/zImage
> error: patch failed: linux/linux.mk:198
> error: linux/linux.mk: patch does not apply
Hmmm, that's weird, it applies fine here on top of these patches.
Let me send another version of these patches then.
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-30 9:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 12:27 [Buildroot] [PATCHv3 0/6] Add some support for device tree kernels Maxime Ripard
2012-07-17 12:27 ` [Buildroot] [PATCH 1/6] Revert "Microblaze: build kernel with device tree" Maxime Ripard
[not found] ` <CAEBucnCan1vRHv4GkhYXGHnrb3Nrtg0rOtwiLY_fTuARuV0W2g@mail.gmail.com>
2012-07-18 7:23 ` Maxime Ripard
2012-07-17 12:27 ` [Buildroot] [PATCH 2/6] Rework support for the device tree Maxime Ripard
2012-07-27 19:45 ` Arnout Vandecappelle
2012-07-17 12:27 ` [Buildroot] [PATCH 3/6] Factorize the u-boot images code Maxime Ripard
2012-07-28 14:36 ` Arnout Vandecappelle
2012-07-17 12:27 ` [Buildroot] [PATCH 4/6] Add support for appended device tree blobs for arm Maxime Ripard
2012-07-28 14:49 ` Arnout Vandecappelle
2012-07-28 19:29 ` Thomas Petazzoni
2012-07-29 15:16 ` Arnout Vandecappelle
2012-07-30 8:25 ` Fabio Porcedda
2012-07-30 8:31 ` Thomas Petazzoni
2012-07-30 10:10 ` Fabio Porcedda
2012-07-17 12:27 ` [Buildroot] [PATCH 5/6] Add cuImage(powerpc) and simpleImage(microblaze) as Linux kernel images variants Maxime Ripard
2012-07-17 12:27 ` [Buildroot] [PATCH 6/6] Update s6lx9 microblaze default configuration Maxime Ripard
2012-07-27 16:06 ` [Buildroot] [PATCHv3 0/6] Add some support for device tree kernels Fabio Porcedda
2012-07-27 18:59 ` Maxime Ripard
2012-07-30 8:33 ` Fabio Porcedda
2012-07-30 9:38 ` Maxime Ripard [this message]
2012-07-30 10:09 ` Fabio Porcedda
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=501655FF.1040501@free-electrons.com \
--to=maxime.ripard@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.