public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 1/2] spl: Move check for SPL_LIBCOMMON support to header
Date: Fri, 20 Jan 2017 15:57:23 -0500	[thread overview]
Message-ID: <20170120205723.GP25981@bill-the-cat> (raw)
In-Reply-To: <547f1960-1437-cb4c-f434-b35fabb21204@ti.com>

On Fri, Jan 20, 2017 at 10:38:41AM -0600, Andrew F. Davis wrote:
> On 01/20/2017 10:25 AM, Tom Rini wrote:
> > On Fri, Jan 06, 2017 at 01:35:44PM -0600, Andrew F. Davis wrote:
> > 
> >> Print statements in SPL depend on lib/common support, so many such
> >> statements are ifdef'd, move the check to the common.h header and
> >> remove these inline checks.
> >>
> >> Signed-off-by: Andrew F. Davis <afd@ti.com>
> >> Reviewed-by: Tom Rini <trini@konsulko.com>
> > 
> > This patch is a good example of why travis-ci is useful, even if takes a
> > few hours for the cycle to complete (kick it off and check the results
> > in the morning :)).  As is, it's broken on PowerPC (where
> > CONFIG_SPL_INIT_MINIMAL is the conditional for puts/printf/etc), mx31pdk
> > and evb-rk3036 (and this is an incomplete list).  The ARM targets are
> > harder to just fix as it shows an underlying problem.  Today we have no
> > single symbol that means "In SPL I want serial output" (and ditto TPL).
> > We try and rely on SPL_SERIAL_SUPPORT but this misses the case where we
> > use neither TINY_PRINTF nor LIBCOMMON but instead have only puts
> > available in a more raw way.  So before we can make the type of change
> > you're doing here we need to introduce a symbol that means "I have
> > output".  That will also greatly reduce the logic needed in the tests in
> > common.h for having puts/etc be real or do-while loops.  Thanks!
> 
> Ahh, I was expecting something like this happening with all the levels
> of ifdef logic involved. Could we keep this patch and add
> CONFIG_SPL_INIT_MINIMAL to the check in common.h?

I did that, but it does not address the problem of mx31pdk and rockchip
and others.

> Removing all these various ifdefs from files is still correct, all this
> ifdef logic should *not* be around calls to puts/etc in-line in the
> code, all we need is to figure out the logic for the function's
> definitions in common.h, which can be cleaned up in a later patch.

Well, thinking about this harder.  What would be OK for now would be a
v2 (that you've pushed through travis-ci) that just removes the tests as
that should be OK.  But... I wonder if we don't have those tests due to
needing to #if out the prints due to the gcc bug[1] that's only fixed in
gcc 6.x and later.

[1]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54303

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170120/34fbb6d9/attachment.sig>

      reply	other threads:[~2017-01-20 20:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 19:35 [U-Boot] [PATCH 1/2] spl: Move check for SPL_LIBCOMMON support to header Andrew F. Davis
2017-01-06 19:35 ` [U-Boot] [PATCH 2/2] spl: Remove inline ifdef check for EXT and FAT support Andrew F. Davis
2017-01-11 16:28   ` Tom Rini
2017-01-19 13:57     ` Simon Glass
2017-01-21  3:37   ` [U-Boot] [U-Boot, " Tom Rini
2017-01-11 16:28 ` [U-Boot] [PATCH 1/2] spl: Move check for SPL_LIBCOMMON support to header Tom Rini
2017-01-20 16:25 ` [U-Boot] [U-Boot, " Tom Rini
2017-01-20 16:38   ` Andrew F. Davis
2017-01-20 20:57     ` Tom Rini [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=20170120205723.GP25981@bill-the-cat \
    --to=trini@konsulko.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