From: Ronny D <ronny_d37@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Linux kernel hang with FDT changes
Date: Thu, 17 Jun 2010 07:28:39 -0700 (PDT) [thread overview]
Message-ID: <565298.93778.qm@web46115.mail.sp1.yahoo.com> (raw)
In-Reply-To: <1276657279.15538.141.camel@xps>
Thanks jerry i verified the fdt fixup code and found problem with my DTB creation.
By adding fixup for timebase-frequency in DTB kernel works fine.
?
-Ronny
--- On Wed, 16/6/10, Jerry Van Baren <gvb.uboot@gmail.com> wrote:
From: Jerry Van Baren <gvb.uboot@gmail.com>
Subject: Re: [U-Boot] Linux kernel hang with FDT changes
To: "Ronny D" <ronny_d37@yahoo.com>
Cc: "Stefan Roese" <sr@denx.de>, "U-boot" <u-boot@lists.denx.de>
Date: Wednesday, 16 June, 2010, 3:01 AM
Hi Ronny,
Just adding to Stefan's comments...
On Mon, 2010-06-14 at 13:27 +0200, Stefan Roese wrote:
> Hi Ronny,
>
> On Monday 14 June 2010 12:00:38 Ronny D wrote:
> > I am using customized ppc440 based board.
>
> BTW: Do you plan to send the U-Boot changes to the mailing list and some time?
>???
> > We have created a .dtb file, u-boot should not update the file because of
> > that we have added following macro in config file
> > #define CONFIG_OF_LIBFDT? ? ? ? ? ? ? ???1
> > #undef CONFIG_OF_BOARD_SETUP?
Is there a reason you *don't* want the board setup to run?
?
> > With the above change kernel code gets hang with following log:
Without the fixup, linux hangs.
[snip]
> > When we debug the u-boot code by added the following flag
> > #define CONFIG_OF_BOARD_SETUP???1
> > Kernel works fine.
> >?
> > Is there any dependency of CONFIG_OF_BOARD_SETUP flag for .dtb file?
With the fixup, it works.
In all cases I'm aware of, the fixup is a *good* thing.? Check the
source to see what is being fixed up.? The evidence is pretty clear that
you want the fixup.
> With CONFIG_OF_BOARD_SETUP defined, the function ft_board_setup() will be
> called to modify the dtb before passing it to the Linux kernel. I suggest you
> check the code to see, what exactly gets changed/patched by this routine.
...and it is a good thing to run unless you have specific reasons not to
run it.? If you really don't want to run the fixup, it is indicating you
have a problem with your DTB (DTS) that you will have to figure out.? As
Stefan points out, the answer lies in the fixup code vs. your DTB.
> Cheers,
> Stefan
Best regards,
gvb
next prev parent reply other threads:[~2010-06-17 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 10:00 [U-Boot] Linux kernel hang with FDT changes Ronny D
2010-06-14 11:27 ` Stefan Roese
2010-06-16 3:01 ` Jerry Van Baren
2010-06-17 14:28 ` Ronny D [this message]
2010-06-17 14:22 ` Ronny D
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=565298.93778.qm@web46115.mail.sp1.yahoo.com \
--to=ronny_d37@yahoo.com \
--cc=u-boot@lists.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