public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Cannot boot mx6qsabred with 2019.07-rc2
Date: Fri, 24 May 2019 00:11:33 +0200	[thread overview]
Message-ID: <67eaac2c-93a5-72e2-03cc-913f9385b598@gmail.com> (raw)
In-Reply-To: <CAOMZO5Aq+V=VR0xMLMOTmpcA1gOsM4cqGs1yFkgNV2NW=qb-2w@mail.gmail.com>

On 5/24/19 12:08 AM, Fabio Estevam wrote:
> On Thu, May 23, 2019 at 7:04 PM Marek Vasut <marek.vasut@gmail.com> wrote:
> 
>> Ah, can't you just use either non-DM/DT SPL (which is OK to do) or
>> combine SPL+DT into a single file , like some other boards do ?
> 
> There are two orthogonal issues we are discussing:
> 
> 1. DM SPL size is beyond the limit for mx6sabresd. Yes, not using DM
> SPL solves the issue here.

I think it makes sense to go this way and fix the MX6 before too many
people get cranky about this forcible DM/DT push , which cripples the
boards left and right.

> 2. Not possible to boot FIT image via SDP. This problem is unrelated
> to number 1 above.

Right

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2019-05-23 22:11 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 17:32 [U-Boot] Cannot boot mx6qsabred with 2019.07-rc2 Fabio Estevam
2019-05-16 17:37 ` Jagan Teki
2019-05-16 18:23   ` Fabio Estevam
2019-05-16 19:40 ` Fabio Estevam
2019-05-16 21:49   ` Lukasz Majewski
2019-05-17  2:21     ` Fabio Estevam
2019-05-17  2:17 ` Peng Fan
2019-05-17  2:22   ` Fabio Estevam
2019-05-17  2:29     ` Peng Fan
2019-05-17 12:39       ` Fabio Estevam
2019-05-17 12:57         ` Lukasz Majewski
2019-05-20 14:07           ` Fabio Estevam
2019-05-20 14:15             ` Jagan Teki
2019-05-23 16:11         ` Jagan Teki
2019-05-23 16:48           ` Fabio Estevam
2019-05-23 17:07             ` Jagan Teki
2019-05-23 17:09               ` Fabio Estevam
2019-05-23 17:26               ` Schrempf Frieder
2019-05-23 17:45                 ` Fabio Estevam
2019-05-23 17:54                   ` Marek Vasut
2019-05-23 17:59                     ` Fabio Estevam
2019-05-23 18:00                       ` Jagan Teki
2019-05-23 18:03                         ` Fabio Estevam
2019-05-23 18:28                       ` Adam Ford
2019-05-23 18:35                         ` Fabio Estevam
2019-05-23 18:37                           ` Adam Ford
2019-05-23 22:03                             ` Marek Vasut
2019-05-23 22:04                       ` Marek Vasut
2019-05-23 22:08                         ` Fabio Estevam
2019-05-23 22:11                           ` Marek Vasut [this message]
2019-05-23 23:14                             ` Fabio Estevam
2019-05-27  6:40                   ` Schrempf Frieder
2019-05-28  0:01                     ` Fabio Estevam
2019-05-31  9:10                     ` Shyam Saini
2019-06-03  6:55                       ` Schrempf Frieder
2019-05-31  6:04               ` Peng Fan
2019-05-24 17:43             ` Tom Rini
2019-05-24 20:08               ` Simon Goldschmidt
2019-05-30 10:06             ` Peng Fan
2019-05-21 13:23       ` Fabio Estevam
2019-05-22  1:38         ` Peng Fan
2019-05-22  2:34           ` Tom Rini
2019-05-22  5:52             ` Lukasz Majewski
2019-05-22 14:23             ` Fabio Estevam
2019-05-22 15:15               ` Tom Rini
2019-05-22 15:49                 ` Marek Vasut
2019-05-22 18:39                 ` Ezequiel Garcia
2019-05-23 13:49           ` Fabio Estevam
2019-05-23 13:59             ` Tom Rini
2019-05-23 14:04               ` Marek Vasut
2019-05-23 15:17                 ` Tom Rini
2019-05-23 17:52                   ` Marek Vasut
2019-05-31  3:21                   ` Peng Fan
2019-05-23 14:08               ` Abel Vesa
2019-05-23 14:33                 ` Tom Rini
2019-05-23 14:47                   ` Michael Nazzareno Trimarchi
2019-05-23 14:50                     ` Tom Rini
2019-05-23 17:51                       ` Marek Vasut

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=67eaac2c-93a5-72e2-03cc-913f9385b598@gmail.com \
    --to=marek.vasut@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox