All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nemanja Savic <vlasinac@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Updating uboot from 2015.04 to 2017.03 - doubts and other questions
Date: Tue, 23 Jul 2019 23:21:53 +0200	[thread overview]
Message-ID: <CAFD_UOd84453MHp4q41-sS_114XXGf_PvmGpg=m4XBjVo4ssGA@mail.gmail.com> (raw)
In-Reply-To: <CAHCN7x+ZW9YyiSYoMh3KxVLYmyKQMHJkR7ZNE0e2Nwrtfi3N9Q@mail.gmail.com>

Thank you Adam for your answer. Sounds like a good starting point for me.
Additionally I would like to ask you further questions regarding your
answers.

> 3. Is device tree used by u-boot the same device tree later used by linu
>
>> > kernel?
>>
>> On my imx6q_logic board, the device tree is appended to the code, but
>> it's only used for U-Boot and or SPL.  SPL is the secondary program
>> loader, and it has a much reduced device tree because of the limited
>> space.  I load a separate device tree for the kernel, because I keep
>> the kernels and their respecive device trees in sync to prevent
>> issues.
>>
>
Does that mean that dtb is already part of the u-boot image? After making
mx6sabreauto_defconfig, the u-boot binary is called something like (I am
not at work at the moment) uboot-dtb.imx, which might imply that dtb is
already part of the binary?

Another question is, which macro or function should I use to print simple
debug messages from the driver function such as probe, etc ...?

Cheers!

      reply	other threads:[~2019-07-23 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 15:23 [U-Boot] Updating uboot from 2015.04 to 2017.03 - doubts and other questions Nemanja Savic
2019-07-23 18:16 ` Adam Ford
2019-07-23 21:21   ` Nemanja Savic [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='CAFD_UOd84453MHp4q41-sS_114XXGf_PvmGpg=m4XBjVo4ssGA@mail.gmail.com' \
    --to=vlasinac@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.