All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] SYS_MALLOC_SIMPLE versus SPL_SYS_MALLOC_SIMPLE?
Date: Mon, 18 Apr 2016 10:54:27 +0200	[thread overview]
Message-ID: <5714A0C3.60608@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1604160432420.10558@localhost.localdomain>

Hi,

On 16-04-16 10:58, Robert P. J. Day wrote:
>
>    (WARNING: many potentially dumb questions coming this weekend as i
> try to put together a u-boot tutorial for some upcoming presentations.
> please be patient ... )
>
>    i had a much longer question about the config option
> SYS_MALLOC_SIMPLE until i noticed that it doesn't seem to be defined
> in a Kconfig file:
>
>    $ grep -rw SYS_MALLOC_SIMPLE *
>    common/malloc_simple.c:#if CONFIG_IS_ENABLED(SYS_MALLOC_SIMPLE)
>    include/exports.h:#if !CONFIG_IS_ENABLED(SYS_MALLOC_SIMPLE)
>    include/_exports.h:#if !CONFIG_IS_ENABLED(SYS_MALLOC_SIMPLE)
>    include/malloc.h:#if CONFIG_IS_ENABLED(SYS_MALLOC_SIMPLE)
>    $
>
> that appears to be the extent of that symbol in the entire u-boot
> source tree, which is obviously different from:
>
>    $ grep -rw SPL_SYS_MALLOC_SIMPLE *
>    arch/arm/Kconfig:	select SPL_SYS_MALLOC_SIMPLE if SUPPORT_SPL
>    arch/arm/mach-rockchip/Kconfig:config SPL_SYS_MALLOC_SIMPLE
>    Kconfig:config SPL_SYS_MALLOC_SIMPLE
>    Kconfig:	depends on SPL_STACK_R && SPL_SYS_MALLOC_SIMPLE
>    $

There is some magic happening somewhere whereby SPL_FOO_BAR
Kconfig settings only get set when builind the SPL and they
actually get set as FOO_BAR, so the SPL_ prefix is special
and tells the u-boot build scripts to only define FOO_BAR
when building the SPL, this goes for all SPL_ prefixed
Kconfig settings. This all is IIRC.

Regards,

Hans

      reply	other threads:[~2016-04-18  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-16  8:58 [U-Boot] SYS_MALLOC_SIMPLE versus SPL_SYS_MALLOC_SIMPLE? Robert P. J. Day
2016-04-18  8:54 ` Hans de Goede [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=5714A0C3.60608@redhat.com \
    --to=hdegoede@redhat.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.