public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Booting non devicetree enabled kernels using u-boot build with CONFIG_OF_LIBFDT ?
Date: Thu, 13 Nov 2014 19:08:59 +0100	[thread overview]
Message-ID: <5464F3BB.3030507@redhat.com> (raw)

Hi all,

So as you know I've been working on getting mainline u-boot to boot the
older android derived linux-sunxi kernels, as some people need features
not yet in mainline, and I would like there to be only one u-boot for both.

I had this working a while ago, but recently it broke, this is caused by
config_distro_defaults.h setting CONFIG_OF_LIBFDT, if I undef that
after including config_distro_defaults.h things work again.

I do not know if CONFIG_OF_LIBFDT is a recent addition to config_distro_defaults.h,
or if something else broke things. But if I do not undef it, boot fails with:

sun7i# bootm start 0x48000000
## Booting kernel from Legacy Image at 48000000 ...
   Image Name:   Linux-3.4.75.sun7i+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3966672 Bytes = 3.8 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
Could not find a valid device tree

Now this can be fixed by removing CONFIG_OF_LIBFDT when CONFIG_OLD_SUNXI_KERNEL_COMPAT
is set, but that is a somewhat big hammer, making it impossible to have one u-boot
build which can boot both old and new kernels with more or less optimal settings.

One theoretical work around is to just pass in a dummy fdt, but that seems silly.

Another option is to allow:

bootm start 0x48000000 - -

To continue with a devicetree, would a patch for that be acceptable ?

Regards,

Hams

             reply	other threads:[~2014-11-13 18:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 18:08 Hans de Goede [this message]
2014-11-13 18:34 ` [U-Boot] Booting non devicetree enabled kernels using u-boot build with CONFIG_OF_LIBFDT ? Tom Rini
2014-11-13 18:38   ` Hans de Goede
2014-11-16 19:41     ` Hans de Goede
2014-11-17  7:24       ` Simon Glass
2014-11-17 14:52     ` Tom Rini
2014-11-17 15:00       ` Hans de Goede

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=5464F3BB.3030507@redhat.com \
    --to=hdegoede@redhat.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