All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] ARM: dts: imx6qdl: Add U-Boot specific device tree files for Cubox-i
Date: Wed, 30 Oct 2019 15:43:39 -0300	[thread overview]
Message-ID: <CAOMZO5D_Esep7_sxiu41_=1LBg5xXnUTL9k__p=gv1pVkigwCA@mail.gmail.com> (raw)
In-Reply-To: <3ab8-5db99c80-15-6c70f70@145192798>

Hi Walter,

On Wed, Oct 30, 2019 at 11:22 AM Walter Lozano
<walter.lozano@collabora.com> wrote:

> Thanks for your comments. My intention was to initially send the device tree patches and in a different patchset update the configuration, as it requires to run different tests (i.e. boot from SATA). Also I felt that this patch has meaning by itself, as it could be useful for people willing to test DM on this board.

It is preferred that you resend the dts pieces only when the cubox
board is really converted to DM, otherwise you are only adding "dead
code".

Also the imx6dl-cubox-i-u-boot.dtb does not need to be explicitly
added in the Makefile.

It gets built automatically by the core U-Boot Makefile logic.

Thanks

  reply	other threads:[~2019-10-30 18:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 14:00 [U-Boot] [PATCH 1/2] ARM: dts: imx6qdl: Add device tree support for SolidRun Cubox-i Walter Lozano
2019-10-28 14:00 ` [U-Boot] [PATCH 2/2] ARM: dts: imx6qdl: Add U-Boot specific device tree files for Cubox-i Walter Lozano
2019-10-28 14:11   ` Fabio Estevam
2019-10-30 14:22     ` [U-Boot] ?==?utf-8?q? ?==?utf-8?q? [PATCH 2/2]?==?utf-8?q? ARM:?==?utf-8?q? " Walter Lozano
2019-10-30 18:43       ` Fabio Estevam [this message]
2019-10-30 19:58         ` [U-Boot] [PATCH 2/2] ARM: " Walter Lozano
2019-11-07 13:48           ` Fabio Estevam
2019-11-07 14:38             ` Walter Lozano

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='CAOMZO5D_Esep7_sxiu41_=1LBg5xXnUTL9k__p=gv1pVkigwCA@mail.gmail.com' \
    --to=festevam@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.