linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: hs@denx.de
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc, 5200: add defconfig for charon board
Date: Mon, 6 Dec 2010 09:49:25 +0100	[thread overview]
Message-ID: <20101206094925.3dd90271@wker> (raw)
In-Reply-To: <4CFC911D.4070306@denx.de>

Hello Heiko,

On Mon, 06 Dec 2010 08:30:37 +0100
Heiko Schocher <hs@denx.de> wrote:

> Hello Wolfram,
> 
> Wolfram Sang wrote:
> > On Sat, Dec 04, 2010 at 09:21:54AM +0100, Heiko Schocher wrote:
> > 
> > There shall be only one mpc5200-defconfig. Does the genric one work with your
> > board?
> 
> Just tried, mpc5200_defconfig works for me, but...
> 
> ... I miss there the LM81 and RTC DS1374 support ... and in another
> patchset from me, I add SM501 support for this board ... also
> for example, I don;t need CONFIG_FB_RADEON*, CONFIG_SPI* defines
> 
> Hmm.. I understand that maintaining the board_defconfigs is a nightmare.
> Just a fast thought (I am not a kconfig expert):
> 
> As there is a mpc5200_defconfig, couldn;t we get rid of the board
> defconfig(s), and add instead a possibility to store only the changes
> against the mpc5200_defconfig in a file? That would save a lot of unneeded
> lines, and maintaining would be easier as common 5200 config options
> are stored in mpc5200_defconfig ... and a "make board_settings" would do:

You can save a reduced config file in ./defconfig by running
"make savedefconfig". This ./defconfig file can also be used as a
board config file in arch/powerpc/configs/52xx/. Look e.g. at the
config files under arch/powerpc/configs/52xx/.

Anatolij

  reply	other threads:[~2010-12-06  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04  8:21 [PATCH 2/2] powerpc, 5200: add defconfig for charon board Heiko Schocher
2010-12-04 21:17 ` Wolfram Sang
2010-12-06  7:30   ` Heiko Schocher
2010-12-06  8:49     ` Anatolij Gustschin [this message]
2010-12-06  9:13       ` Heiko Schocher
2010-12-06  9:31         ` Wolfram Sang
2010-12-06  9:49           ` Heiko Schocher
2010-12-06 10:01             ` Wolfram Sang
2010-12-06 10:25               ` Heiko Schocher

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=20101206094925.3dd90271@wker \
    --to=agust@denx.de \
    --cc=hs@denx.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).