From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/7] lib: Split panic functions out of vsprintf.c
Date: Tue, 8 Dec 2015 13:36:31 -0600 [thread overview]
Message-ID: <1449603391.15946.150.camel@freescale.com> (raw)
In-Reply-To: <CAPnjgZ2v49b51JfQ5-zP-C5RD_hswTTdUYiM7Gs6_WXzydR=Ow@mail.gmail.com>
On Tue, 2015-12-08 at 12:34 -0700, Simon Glass wrote:
> Hi Sjoerd,
>
> On 8 December 2015 at 00:27, Sjoerd Simons
> <sjoerd.simons@collabora.co.uk> wrote:
> >
> > On Mon, 2015-12-07 at 17:39 -0700, Simon Glass wrote:
> > > > diff --git a/lib/Makefile b/lib/Makefile
> > > > index 1f1ff6f..ae84833 100644
> > > > --- a/lib/Makefile
> > > > +++ b/lib/Makefile
> > > > @@ -85,13 +85,13 @@ obj-$(CONFIG_LIB_RAND) += rand.o
> > > > ifdef CONFIG_SPL_BUILD
> > > > # SPL U-Boot may use full-printf, tiny-printf or none at all
> > > > ifdef CONFIG_USE_TINY_PRINTF
> > > > -obj-$(CONFIG_SPL_SERIAL_SUPPORT) += tiny-printf.o
> > > > +obj-$(CONFIG_SPL_SERIAL_SUPPORT) += tiny-printf.o panic.o
> > > > else
> > > > -obj-$(CONFIG_SPL_SERIAL_SUPPORT) += vsprintf.o
> > > > +obj-$(CONFIG_SPL_SERIAL_SUPPORT) += vsprintf.o panic.o
> > > > endif
> > > > else
> > > > # Main U-Boot always uses the full printf support
> > > > -obj-y += vsprintf.o
> > > > +obj-y += vsprintf.o panic.o
> > > > endif
> > >
> > > Why not just add this outside all the ifdef stuff:
> > >
> > > obj-y += panic.o
> >
> > Just keeping the old behaviour, that code was not build for SPL builds
> > without serial support before. Do you see a benefit of just always
> > building it ?
>
> I cannot see a case where you don't build it:
>
> ifdef CONFIG_SPL_BUILD
> # SPL U-Boot may use full-printf, tiny-printf or none at all
> ifdef CONFIG_USE_TINY_PRINTF
> obj-$(CONFIG_SPL_SERIAL_SUPPORT) += tiny-printf.o panic.o strto.o
> else
> obj-$(CONFIG_SPL_SERIAL_SUPPORT) += vsprintf.o panic.o strto.o
> endif
> else
> # Main U-Boot always uses the full printf support
> obj-y += vsprintf.o panic.o strto.o
> endif
>
>
> Every case has panic.o and strto.o. What am I missing?
The dependency on CONFIG_SPL_SERIAL_SUPPORT.
-Scott
next prev parent reply other threads:[~2015-12-08 19:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 22:27 [U-Boot] [PATCH 0/7] Switch rockchip firefly to using tiny-printf Sjoerd Simons
2015-12-04 22:27 ` [U-Boot] [PATCH 1/7] spl: use panic_str instead of panic Sjoerd Simons
2015-12-06 16:45 ` Simon Glass
2015-12-08 0:39 ` Simon Glass
2015-12-14 3:44 ` Simon Glass
2015-12-04 22:27 ` [U-Boot] [PATCH 2/7] spl: mmc: Explicitly init mmc struct Sjoerd Simons
2015-12-06 16:45 ` Simon Glass
2015-12-04 22:27 ` [U-Boot] [PATCH 3/7] lib/tiny-printf.c: Implement vprintf Sjoerd Simons
2015-12-08 0:39 ` Simon Glass
2015-12-14 3:44 ` Simon Glass
2015-12-04 22:27 ` [U-Boot] [PATCH 4/7] lib: Split panic functions out of vsprintf.c Sjoerd Simons
2015-12-08 0:39 ` Simon Glass
2015-12-08 7:27 ` Sjoerd Simons
2015-12-08 19:34 ` Simon Glass
2015-12-08 19:36 ` Scott Wood [this message]
2015-12-08 19:38 ` Simon Glass
2015-12-14 3:45 ` Simon Glass
2015-12-14 7:38 ` Sjoerd Simons
2015-12-04 22:27 ` [U-Boot] [PATCH 5/7] lib: split out strtoxxxx " Sjoerd Simons
2015-12-08 0:39 ` Simon Glass
2015-12-08 7:30 ` Sjoerd Simons
2015-12-14 3:45 ` Simon Glass
2015-12-04 22:27 ` [U-Boot] [PATCH 6/7] mmc: mmc: Don't use sprintf when using tiny-printf Sjoerd Simons
2015-12-08 0:40 ` Simon Glass
2015-12-08 7:34 ` Sjoerd Simons
2015-12-14 3:45 ` Simon Glass
2015-12-04 22:27 ` [U-Boot] [PATCH 7/7] rockchip: firefly: Use tiny-printf Sjoerd Simons
2015-12-08 0:40 ` Simon Glass
2015-12-14 3:45 ` Simon Glass
2015-12-05 10:00 ` [U-Boot] [PATCH 0/7] Switch rockchip firefly to using tiny-printf Stefan Roese
2015-12-07 21:43 ` Simon Glass
2015-12-07 21:53 ` Tom Rini
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=1449603391.15946.150.camel@freescale.com \
--to=scottwood@freescale.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