public inbox for u-boot@lists.denx.de
 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: Sun, 19 Dec 2010 17:05:45 -0500	[thread overview]
Message-ID: <201012191705.46162.vapier@gentoo.org> (raw)
In-Reply-To: <20101219200945.0633C14F1BA@gemini.denx.de>

On Sunday, December 19, 2010 15:09:44 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > > I want to get rid of all these board specific config.mk files.
> > > And I don't see a good reason why it would be needed here.  Other
> > > boards don;t need any of this either.
> > 
> > then where exactly are boards supposed to specify their own custom build
> > settings ?  like optimizations that they want to enable on specific
> 
> Boards should not need custom build rules in the first place.

i didnt say build rules, i said settings.  that means tweaking things like 
CFLAGS.  none of the Blackfin board config.mk's have custom build rules.

> > files/subdirs ?  many Blackfin boards prefer speed over size in the
> > compression code because we arent hurting for space, and most people
> > prefer the faster decompression at runtime.  without a board config.mk,
> > that isnt possible.
> 
> Can these be gobal settings for all BF boards then?

no, that doesnt make any sense.  just because i want some of the boards i 
maintain to favor speed over size doesnt mean every board maintainer should.  
thus the settings are in the board-specific config.mk where they should be.
-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/20101219/d5a694aa/attachment.pgp 

  reply	other threads:[~2010-12-19 22:05 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 [this message]
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
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=201012191705.46162.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox