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: Thu, 23 May 2019 19:51:07 +0200	[thread overview]
Message-ID: <e60d0882-0bc4-1af1-3ff7-fecc1b1127cc@gmail.com> (raw)
In-Reply-To: <20190523145035.GD22232@bill-the-cat>

On 5/23/19 4:50 PM, Tom Rini wrote:
> On Thu, May 23, 2019 at 04:47:59PM +0200, Michael Nazzareno Trimarchi wrote:
>> Hi
>>
>> On Thu, May 23, 2019 at 4:33 PM Tom Rini <trini@konsulko.com> wrote:
>>>
>>> On Thu, May 23, 2019 at 02:08:23PM +0000, Abel Vesa wrote:
>>>> On 19-05-23 09:59:05, Tom Rini wrote:
>>>>> On Thu, May 23, 2019 at 10:49:11AM -0300, Fabio Estevam wrote:
>>>>>> Hi Peng,
>>>>>>
>>>>>> On Tue, May 21, 2019 at 10:38 PM Peng Fan <peng.fan@nxp.com> wrote:
>>>>>>
>>>>>>>> I will send a v2 removing CONFIG_SPL_DM.
>>>>>>>
>>>>>>> So what is the real direction moving to use SPL driver, non-dm is allowed in future?
>>>>>>
>>>>>> We are very limited in space when CONFIG_SPL_DM is used on imx6q-sabresd.
>>>>>>
>>>>>> With CONFIG_SPL_DM selected the size increase due to the three dtb's
>>>>>> is about 8kB.
>>>>>>
>>>>>> Even with CONFIG_SPL_DM disabled we ony have 1kB of free space, so I
>>>>>> still want to optimize the size further.
>>>>>
>>>>> So with CONFIG_SPL_DM we're overflowing by ~7kB?
>>>>
>>>> Well, the mandatory requirements here are as follow (AFAIK):
>>>> 1. keep one binary for all imx6dl imx6[qp|dl|q]-sabresd
>>>> 2. have DM support in SPL
>>>>
>>>> So I guess we have to either prioritize the other needed configs and
>>>> leave out the one we can do without. That, ofcourse, if we still want
>>>> to fit in and we still want one binary for all three sabresd boards.
>>>
>>> Well, no, you don't have to use DM in SPL.  But what I'm wondering is if
>>> we need qp/dl/q specific information at the SPL stage or if that can
>>> wait until we're doing the real U-Boot.
>>
>> Is dcd table take space?
> 
> The DCD table is included in that hard size limit, but yes, if there's
> QP/DL/Q specific stuff that we could handle via the plugin mechanism or
> similar, that might be part of the solution.

You do need Q/DL/S specific stuff in SPL for e.g. pinmux .
And you want to minimize the DCD table and move all that logic into SPL,
since the DCD is rather limited.

-- 
Best regards,
Marek Vasut

      reply	other threads:[~2019-05-23 17:51 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
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 [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=e60d0882-0bc4-1af1-3ff7-fecc1b1127cc@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