All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Blackfin: bf525-ucr2: new board port
Date: Mon, 20 Dec 2010 17:31:45 -0500	[thread overview]
Message-ID: <201012201731.47283.vapier@gentoo.org> (raw)
In-Reply-To: <20101220210520.96AC8125CF95@gemini.denx.de>

On Monday, December 20, 2010 16:05:20 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > > And why cannot it be set in the board config file like every other
> > > board doing it?
> > 
> > ive explained in the past why.  one of the reasons why i think config.mk
> > makes more sense is this setting is only used for compilation (build
> > flags).  it isnt used directly anywhere in the config.h or related code.
> >  i also find it significantly cleaner than the cpu handling as found in
> > the arm or m68k or ppc ports where copy & pasting swaths of code is the
> > rule.
> 
> OK, so this is a "I think it makes more sense" and a "I find it
> cleaner".  There was no "cannot", as far as I can tell.

things can be moved back, but it would require ugly hacks in the Blackfin code 
to pull it back out.  if you want to live with the ugly hacks as a trade off 
of getting rid of a few more Blackfin config.mk's (but not all), then that is 
possible.

note that these issues shouldnt hold up merging a board which is working the 
way it should as the other boards.

> I think it makes a lot of sense to try and move all board specific
> configuration settings into a single file (the board config file);
> this will, among other things, make it easier to make such settings
> accessable through some config tool - assume somebody wants to take
> steps toward Kconfig or such.

i dont see how Kconfig would be relevant.  the point of Kconfig is to let 
users configure optional features, not aspects burned into hardware.  letting 
people pick a processor that isnt on the board makes no sense.  linux 
specifically has followed this style -- the way the board is physically wired 
up is in the platform resources, not Kconfig.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20101220/ed1ee832/attachment.pgp 

  reply	other threads:[~2010-12-20 22:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 10:48 [U-Boot] [PATCH] Blackfin: bf525-ucr2: new board port Mike Frysinger
2010-12-18 23:14 ` Wolfgang Denk
2010-12-19  4:40   ` Mike Frysinger
2010-12-19 12:25     ` Wolfgang Denk
2010-12-19 16:33       ` Mike Frysinger
2010-12-19 20:09         ` Wolfgang Denk
2010-12-19 22:05           ` Mike Frysinger
2010-12-19 21:20             ` Wolfgang Denk
2010-12-19 23:18               ` Mike Frysinger
2010-12-20 10:49                 ` Wolfgang Denk
2010-12-20 19:36                   ` Mike Frysinger
2010-12-20 21:05                     ` Wolfgang Denk
2010-12-20 22:31                       ` Mike Frysinger [this message]
2010-12-20 22:56                         ` Wolfgang Denk
2010-12-21  0:24                           ` Mike Frysinger
2010-12-21  5:37                             ` Wolfgang Denk
2010-12-22 15:38                               ` Mike Frysinger

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=201012201731.47283.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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.