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):
- keep one binary for all imx6dl imx6[qp|dl|q]-sabresd
- 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.