From: Jerry Van Baren <gvb.linuxppc.dev@gmail.com>
To: Peter Czanik <pczanik@fang.fa.gau.hu>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>, Wolfgang Denk <wd@denx.de>
Subject: Re: Default flats for running dtc from kernel build
Date: Sun, 15 Jun 2008 23:00:46 -0400 [thread overview]
Message-ID: <4855D75E.1050904@gmail.com> (raw)
In-Reply-To: <484CFB11.1080400@fang.fa.gau.hu>
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@8000 first_busno=0 last_busno=0
> pcie@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
prev parent reply other threads:[~2008-06-16 3:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 9:05 [PATCH v2 1/4] [POWERPC] 85xx: add board support for the TQM8548 modules Wolfgang Grandegger
2008-06-05 13:43 ` Kumar Gala
2008-06-05 17:19 ` Wolfgang Grandegger
2008-06-05 22:52 ` David Gibson
2008-06-06 10:09 ` Wolfgang Grandegger
2008-06-06 13:59 ` Kumar Gala
2008-06-06 14:33 ` Wolfgang Denk
2008-06-06 14:51 ` Default flats for running dtc from kernel build Kumar Gala
2008-06-06 15:31 ` Jon Loeliger
2008-06-06 15:42 ` Kumar Gala
2008-06-06 15:44 ` Grant Likely
2008-06-06 16:08 ` Jon Loeliger
2008-06-06 21:39 ` Segher Boessenkool
2008-06-09 9:42 ` Peter Czanik
2008-06-16 3:00 ` Jerry Van Baren [this message]
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=4855D75E.1050904@gmail.com \
--to=gvb.linuxppc.dev@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=pczanik@fang.fa.gau.hu \
--cc=wd@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).