From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Wolfgang Denk" <wd@denx.de>
Cc: Olof Johansson <olof@lixom.net>,
linuxppc-dev@ozlabs.org, tech-denx@semihalf.com,
Detlev Zundel <dzu@denx.de>, Marian Balakowicz <m8@semihalf.com>
Subject: Re: [PATCH] [POWERPC] Update TQM5200, CM5200 and Motion-PRO _defconfig and .dts files
Date: Wed, 23 Jan 2008 09:27:15 -0700 [thread overview]
Message-ID: <fa686aa40801230827s5a7b3ea9s770abaf0ad2838b8@mail.gmail.com> (raw)
In-Reply-To: <20080123125413.EB56924344@gemini.denx.de>
On 1/23/08, Wolfgang Denk <wd@denx.de> wrote:
> In message <479725A4.2020401@semihalf.com> you wrote:
> > Olof Johansson wrote:
> > ...
> > >
> > > I disagree, I have one defconfig for all our boards to date. It means I
> > > only have one kernel to build to test on all boards, instead of having
> > > to build a number of different kernels. Keeping it fairly generic also
> > > means a customer can start out using the generic kernel in case they
> > > want to, and later on add their own drivers and prune out what is not
> > > needed.
> >
> > Well, I just prefer separate defconfigs but I can live with the common
> > one as well, feel free to merge it as you see it fit.
>
> Well, it may make sense to use common defconfig files for boards of
> the same breed (different configurations of one board family from one
> vendor for example). But please note that TQM5200, CM5200 and
> Motion-PRO are boards from 3 different vendors, used by different
> projects with differing needs. IMO it makes very much sense to
> provide 3 separate default configurations that match the specific
> requirements of each of these boards.
>
> In this case I vote for separate defconfig files, please.
I think I'm going to go with a single defconfig for all 5200 boards
for the time being. We can revisit later if it turns out not to be
working. Here are my reasons:
- mpc5200 is intended to be multiplatform. Using a common defconfig
increases the likelyhood that a kernel with support for all 5200
platforms will actually get tested.
- Reduces the time cost required to build all powerpc defconfigs (only
1 needed instead of 5 and growing)
- defconfigs are intended to be the known working configuration; not
necessarily an optimized for deployment configuration. The
system/kernel engineer is still responsible to tailor the
configuration for a shippable distribution.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2008-01-23 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 14:31 [PATCH] [POWERPC] Update TQM5200, CM5200 and Motion-PRO _defconfig and .dts files Marian Balakowicz
2008-01-17 16:05 ` Grant Likely
2008-01-17 18:02 ` Marian Balakowicz
2008-01-17 18:23 ` Grant Likely
2008-01-17 22:05 ` Marian Balakowicz
2008-01-18 3:41 ` Olof Johansson
2008-01-23 11:31 ` Marian Balakowicz
2008-01-23 12:54 ` Wolfgang Denk
2008-01-23 16:27 ` Grant Likely [this message]
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=fa686aa40801230827s5a7b3ea9s770abaf0ad2838b8@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dzu@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=m8@semihalf.com \
--cc=olof@lixom.net \
--cc=tech-denx@semihalf.com \
--cc=wd@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;
as well as URLs for NNTP newsgroup(s).