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] Cannot boot mx6qsabred with 2019.07-rc2
Date: Thu, 23 May 2019 10:49:11 -0300	[thread overview]
Message-ID: <CAOMZO5Bzd7=ZJ59FPPor0G0QwNnAg4_hCgw1qHjDXtYq_dO2tQ@mail.gmail.com> (raw)
In-Reply-To: <AM0PR04MB4481B9A748A56F1D71DC2D1488000@AM0PR04MB4481.eurprd04.prod.outlook.com>

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.

Two options that I want also to remove are:

CONFIG_SPL_FS_EXT4=y
CONFIG_SPL_I2C_SUPPORT=y

We are at -rc2 now, and I would really like to have mx6sabresd booting again.

Please check my v2 series and see if it looks good.

Thanks

  parent reply	other threads:[~2019-05-23 13:49 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 [this message]
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='CAOMZO5Bzd7=ZJ59FPPor0G0QwNnAg4_hCgw1qHjDXtYq_dO2tQ@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.