Default flats for running dtc from kernel build
Jerry Van Baren
gvb.linuxppc.dev at gmail.com
Mon Jun 16 13:00:46 EST 2008
Peter Czanik wrote:
> Hello,
>
> Kumar Gala írta:
>> diff --git a/arch/powerpc/boot/Makefile b/arch/powerpc/boot/Makefile
>> index c40fb82..52db85a 100644
>> --- a/arch/powerpc/boot/Makefile
>> +++ b/arch/powerpc/boot/Makefile
>> @@ -29,6 +29,8 @@ ifdef CONFIG_DEBUG_INFO
>> BOOTCFLAGS += -g
>> endif
>>
>> +DTS_FLAGS ?= -R4 -S 0x3000
>> +
>> ifeq ($(call cc-option-yn, -fstack-protector),y)
>> BOOTCFLAGS += -fno-stack-protector
>> endif
> I have a 8610 standing next to my desk with U-Boot 1.3.0 (Mar 13 2008 -
> 10:14:26). It came with 2.6.23. I wanted to compile a kernel from the
> latest available kernel sources ( 2.6.26-RC5-git2 ). I compiled it using
> mpc8610_hpcd_defconfig. I also did a make mpc8610_hpcd.dtb to have a
> matching dtb file for the kernel. This is how far it gets:
>
> => boot
>
> 11032 bytes read
>
> 1708346 bytes read
> ## Booting image at 01000000 ...
> Image Name: Linux-2.6.26-rc5-git2-czp7
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size: 1708282 Bytes = 1.6 MB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> Uncompressing Kernel Image ... OK
> Booting using the fdt at 0xc00000
> Loading Device Tree to 007fb000, end 007fdb17 ... OK
>
> When I use the 2.6.26 kernel, but the original dtb file from the BSP,
> then I get two more lines on the serial console:
>
> pci at 8000 first_busno=0 last_busno=0
> pcie at 9000 first_busno=0 last_busno=0
>
> So I suspected, that this might be something with the dtb file. This is
> when I ran into this thread. I tried all the different options for
> DTS_FLAGS to generate a working dtb file, but I got the same result,
> "Loading Device Tree to 007fb000, end 007fdb17 ... OK" was the last line
> on screen. Any additional ideas, how to create a working dtb file for
> the 8610 board for later kernels?
>
> Bye,
> CzP
Hi Peter,
Does your .dts (dtb source) have an /aliases node with properties
pointing to the proper serial port(s) (and enthernet port(s))?
Somewhere around the timeframe of your current u-boot/linux versions,
the /aliases node was added to tell the kernel which serial was ttyS0,
ttyS1, etc. in an independent way.
I would strongly recommend a new u-boot too. The merge window for 1.3.4
just closed, it should work well for you. If not, fix patches are
welcome on the u-boot list. ;-)
HTH,
gvb
More information about the Linuxppc-dev
mailing list