public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc4xx: Enable support for 64bit printf on all PPC4xx variants
Date: Wed, 08 Jul 2009 22:01:23 +0200	[thread overview]
Message-ID: <20090708200123.BBAB3832E416@gemini.denx.de> (raw)
In-Reply-To: <200907061739.33498.sr@denx.de>

Dear Stefan Roese,

In message <200907061739.33498.sr@denx.de> you wrote:
>
> > Please move these CONFIG_SYS_* settings out of this file.
> >
> > For me it is not acceptable to set configuration options in global
> > header files like include/ppc4xx.h; CONFIG_* settings are supposed to
> > be selected by the board configuration files, and only there.
> 
> I don't share this opinion. I think it's perfectly valid to enable CONFIG_* 
> settings in global header files (or some other global files). Sometimes there 
> are dependencies that can (or even should) be solved this way. One example is 
> the 4xx NAND driver which needs to configure/set CONFIG_MTD_NAND_ECC_SMC for 
> correct operation. This is currently done directly in 

In such a case please do not name the varoable CONFIG_.

Rule is: CONFIG_* and CONFIG_SYS_* are to be set / unset in the board
configuration files only (eventually with help of trickery  from  the
top level Makefile).

> drivers/mtd/nand/nand_ecc.c. The plan also proposed by Scott Wood is to remove 
> this define from this file once we have the Kconfig framework intact. Then 
> Kconfig will enable this define as a dependency for PPC4xx. As you know this 
> is common praxis in Linux as well.

Using Kconfig is one thing, and OK.

To me this is even more reason to forbid using CONFIG_* and
CONFIG_SYS_* outside board config files.

> > I hope we don't have any more such #defines hidden in other header
> > files?
> 
> I vote for completely removing these defines then (or at least 
> CONFIG_SYS_64BIT_VSPRINTF) and by this enabling the 64bit printf format for 
> all boards. I myself have hunted problems disguised by incorrect 64bit 

I don't want this because of the memory footprint.

Actually I'm pretty much annoyed we need this at all.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Where there's no emotion, there's no motive for violence.
	-- Spock, "Dagger of the Mind", stardate 2715.1

  reply	other threads:[~2009-07-08 20:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06  9:48 [U-Boot] [PATCH] ppc4xx: Enable support for 64bit printf on all PPC4xx variants Stefan Roese
2009-07-06 11:17 ` Wolfgang Denk
2009-07-06 15:39   ` Stefan Roese
2009-07-08 20:01     ` Wolfgang Denk [this message]
2009-07-08 21:11       ` Scott Wood
2009-07-08 21:24         ` Wolfgang Denk
2009-07-08 21:29           ` Scott Wood
2009-07-08 21:57             ` Wolfgang Denk
2009-07-08 22:27               ` Scott Wood
2009-07-09  4:57                 ` Stefan Roese
2009-07-09  7:41                 ` Wolfgang Denk
2009-07-08 22:18         ` Jerry Van Baren
2009-07-08 22:27           ` Scott Wood
2009-07-09  5:00           ` Stefan Roese
2009-07-09 12:24             ` Jerry Van Baren
2009-07-09 12:48               ` Stefan Roese
2009-07-09 13:02                 ` Jerry Van Baren
2009-07-09  4:54       ` Stefan Roese
2009-07-17 18:44         ` Wolfgang Denk

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=20090708200123.BBAB3832E416@gemini.denx.de \
    --to=wd@denx.de \
    --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