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-Users] [RFC] u-boot migration to kconfig
Date: Mon, 24 Sep 2007 11:37:14 +0200	[thread overview]
Message-ID: <20070924093714.DAD5F2408B@gemini.denx.de> (raw)
In-Reply-To: Your message of "Sun, 23 Sep 2007 23:53:38 +0200." <C31CAD02.3BD8%plagnioj@jcrosoft.com>

In message <C31CAD02.3BD8%plagnioj@jcrosoft.com> you wrote:
> 
> >>     arch/arm/boot <- where will be store the u-boot & u-boot.bin
> > 
> > I don't see a use for this. What's wroing with having these  files  in
> > the top level directory?
> 
> The problem is when you work on multiple architecture & board.
> But it's most cosmetic.

What is your problem with such a setup? You do use "make O=..." then,
don't you?

> >>     arch/arm/config/ <- defconfig
> > 
> > Please don't. Please add the default  config  files  into  the  board
> > directory. That's IMHO where they logically belong.
> 
> It's not in the board directory, it's in the arch directory.
> 
> As example when you specify your architecture by ARCH=arm
> And do a make help only the sh default configuration can be accessible and
> show.

I would like to avoid having board  specific  information  scapttered
over several files *and* directories. So far, we know that everything
(except for a "few" #ifdef's ;-) is concentrated in board/<name>/ and
include/configs/<name>.h

This is a *very* useful setup, me thinks. [Actually  I'  rather  thae
the <name>.h config file in the board driectpory, too, but that would
make the Makefile (as it is currently) too complicated.

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
"The best index to a person's character is a) how  he  treats  people
who can't do him any good and b) how he treats people who can't fight
back."                                            - Abigail Van Buren

  parent reply	other threads:[~2007-09-24  9:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22 10:27 [U-Boot-Users] [RFC] u-boot migration to kconfig Jean-Christophe PLAGNIOL-VILLARD
2007-09-22 15:41 ` Grant Likely
2007-09-22 17:18   ` Jean-Christophe PLAGNIOL-VILLARD
2007-09-22 19:08     ` Wolfgang Denk
2007-09-22 21:06       ` Jean-Christophe PLAGNIOL-VILLARD
2007-09-22 22:32         ` Grant Likely
2007-09-23 18:10           ` Jean-Christophe PLAGNIOL-VILLARD
2007-09-23 21:37             ` Wolfgang Denk
2007-09-23 21:53               ` Jean-Christophe PLAGNIOL-VILLARD
2007-09-24  5:06                 ` Grant Likely
2007-09-24  9:37                 ` Wolfgang Denk [this message]
2007-09-24 21:22                   ` Jean-Christophe PLAGNIOL-VILLARD
2007-09-23 22:13               ` Ulf Samuelsson
2007-09-24  3:31                 ` Shinya Kuribayashi
2007-09-24  5:12                   ` Grant Likely
2007-09-24  5:52                     ` Shinya Kuribayashi
2007-09-24  8:18                       ` Ulf Samuelsson
2007-09-24  8:15                     ` Ulf Samuelsson
2007-09-24  8:09                   ` Ulf Samuelsson
2007-09-24  9:40                 ` Wolfgang Denk
2007-09-24 11:16                   ` Ulf Samuelsson
2007-09-24  4:58             ` Grant Likely
2007-09-24  8:47               ` Haavard Skinnemoen
  -- strict thread matches above, loose matches on Subject: below --
2007-09-13 23:28 Grant Likely
2007-09-14 17:11 ` Jon Loeliger
2007-09-14 22:20   ` 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=20070924093714.DAD5F2408B@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