Passing devicetree to kernel

Raj Swaminathan rajshyam at
Thu Aug 13 09:58:51 PDT 2015

Hi Lucas,

I am using Altera's cyclone 5 SoCFPGA.

Barebox version 2015.04.0
Linux is rocketboards version 3.18.0

I put some debug statements into the code at common/bootm.c and found
that the internal device tree is being used and it is the right
version. The problem is probably in the way I'm manipulating the
devicetree in barebox. I'm trying to enable some devices and fill up
the mac address field in barebox before i hand off the same devicetree
to the kernel.  One way i have gotten around the problem is to keep 2
versions of the devicetree but have barebox open the kernel devicetree
file and modify it.


On Thu, Aug 13, 2015 at 8:39 AM, Lucas Stach <l.stach at> wrote:
> Hi Raj,
> Am Mittwoch, den 12.08.2015, 10:21 -0700 schrieb Raj Swaminathan:
>> Hi,
>> The barebox documentation is a little vague on how the internal device
>> tree is actually passed to the kernel.  I was previously using this
>> environment setting to pass the kernel's devicetree to the kernel:
>> global.bootm.oftree=${PATH}/devicetree
>> My understanding was taking out that line would be sufficient.
>> Unfortunately I can no longer get my kernel to boot. It stalls here:
>> Loading ARM Linux zImage '/boot/linux'
>> commandline:  console=ttyS0,115200 earlyprintk  root=LABEL=root rw rootwait
> Can you be more specific? What's the system/architecture you are using?
> Which version of barebox is this and which kernel version are you trying
> to start?
> Regards,
> Lucas
> --
> Pengutronix e.K.             | Lucas Stach                 |
> Industrial Linux Solutions   |  |

More information about the barebox mailing list