public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Riscv: CONFIG_DEFAULT_DEVICE_TREE failures
Date: Wed, 3 Apr 2019 07:18:43 -0400	[thread overview]
Message-ID: <20190403111843.GD4664@bill-the-cat> (raw)
In-Reply-To: <DFBFAE09-3505-48D1-B817-89DD4A8790D8@sifive.com>

On Tue, Apr 02, 2019 at 03:16:10PM -0500, Troy Benjegerdes wrote:
> 
> > On Mar 31, 2019, at 5:02 PM, Tom Rini <trini@konsulko.com> wrote:
> > 
> > On Fri, Mar 29, 2019 at 11:15:48PM -0700, Troy Benjegerdes wrote:
> > 
> >> I attempted to merge in the latest master branch into
> >> https://github.com/sifive/u-boot/tree/sandbox and I got
> >> the following error, which seems somewhat broken..
> >> 
> >> 
> >> Device Tree Source is not correctly specified.
> >> Please define 'CONFIG_DEFAULT_DEVICE_TREE'
> >> or build with 'DEVICE_TREE=<device_tree>' argument
> >> 
> >> dts/Makefile:28: recipe for target 'arch/riscv/dts/fu540.dtb' failed
> >> 
> >> 
> >> Does anyone have any idea what would have caused that?
> >> 
> >> Also any feedback or pointers on why the serial_sifive.c 
> >> driver with CONFIG_DM_SERIAL would not work, but serial_hifive.c
> >> without CONFIG_DM_SERIAL does seem to work might be appreciated.
> > 
> > You'll need to do something like
> > 
> > commit 89c2b5c02049aea746b1edee0b4e1d8519dec2f4
> > Author: Masahiro Yamada <yamada.masahiro@socionext.com>
> > Date:   Thu Mar 14 14:58:33 2019 +0900
> > 
> >    ARM: fix arch/arm/dts/Makefile
> > 
> >    Since commit 27cb7300ffda ("Ensure device tree DTS is compiled"),
> >    build succeeds irrespective of the correctness of Makefile.
> > 
> >    In fact, you can compile any defconfig without adding any entry in
> >    arch/*/dts/Makefile.
> > 
> >    As a result, a lot of wrong code have been merged unnoticed.
> > 
> >    I am going to revert that commit, and lots of hidden issues have
> >    come to light:
> > 
> >    [1] Typos
> > 
> >      armada-3720-uDPU.dts, sun8i-a83t-tbs-a711.dts
> > 
> >      use the extension ".dts" instead of ".dtb"
> > 
> >    [2] DTB is associated to undefined CONFIG option
> > 
> >      For example, mx6sllevk_defconfig defines CONFIG_MX6SLL, but
> >      associates its device tree to CONFIG_MX6SL, which is undefined.
> > 
> >    [3] Lots of entries are missing
> > 
> >    Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> >    Reviewed-by: Chris Packham <judge.packham@gmail.com>
> >    [trini: add imx6ul pico dtbs]
> >    Signed-off-by: Tom Rini <trini@konsulko.com>
> > 
> > But to arch/riscv/dts/Makefile
> 
> I ended up reverting that commit, and we now have
> https://github.com/sifive/u-boot/tree/sandbox booting to a prompt
> based on upstream master.

Note that you just need something like:
obj-y += first.dtb \
         second.dtb

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190403/a37cf0fa/attachment.sig>

  reply	other threads:[~2019-04-03 11:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-30  6:15 [U-Boot] Riscv: CONFIG_DEFAULT_DEVICE_TREE failures Troy Benjegerdes
2019-03-31 22:02 ` Tom Rini
2019-04-02 20:16   ` Troy Benjegerdes
2019-04-03 11:18     ` Tom Rini [this message]
2019-04-03 11:21       ` Masahiro Yamada
2019-04-03 11:29         ` Tom Rini

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=20190403111843.GD4664@bill-the-cat \
    --to=trini@konsulko.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