linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Please pull linux-2.6-mpc52xx.git
Date: Mon, 17 Mar 2008 23:28:36 +0100	[thread overview]
Message-ID: <20080317222836.AFA66241A2@gemini.denx.de> (raw)
In-Reply-To: Your message of "Mon, 17 Mar 2008 15:43:43 CST." <fa686aa40803171443q7a53f0balbb49740116c6552@mail.gmail.com>

In message <fa686aa40803171443q7a53f0balbb49740116c6552@mail.gmail.com> you wrote:
>
> b) defconfigs is more about testing and a known working configuration
> than it is about a distribution configuration.  It's not intended to
> be the deployed config.  For a distribution/deployable image it is
> expected that the engineer responsible will tailor the config.

This may be true in general, but for the boards in question it is
definitely incorrect:

* The TQM5200 configuration as provided is intended for  shipping  as
  default  configuration  for  this board. The "engineer responsible"
  already *did* the tailoring and put that  state  in  the  defconfig
  file.

* The CM5200 and Motion-Pro boards are custom designs, where the
  defconfig file matches exactly the requirements of the respective
  customers.

I feel it is very important to be able to include this  configuration
information  somewhere  with  the  kernel source tree - and to me the
defconfig file for a board is the most  natural  place  to  put  such
information.

Please understand that we do  NOT  expect  the  end  user  having  to
"tailor  the  config"  -  instead,  we  want  to  provide  a  default
configuration that can be used as is,  at  least  for  default  usage
cases.


If you don't want to use a board specific default configuration, then
please tell me what the recommended way is to provide a knwon  to  be
working,  tested  *and*  *useful*  default  configuration  for custom
boards in the Linux kernel tree?


> All these boards are supported with
> arch/powerpc/platforms/mpc5200_simple.c.  A kernel built for that
> platform will boot on any of those boards as long as it is passed the
> correct device tree.

I don't doubt that the kernel will boot. But that does not mean  that
it   is  ready  for  use  for  the  intended  purpose.  For  example,
arch/powerpc/platforms/52xx/motionpro.c contains code to  setup  some
custom   LEDs   on   this   board.   I   can't   find  that  code  in
arch/powerpc/platforms/mpc5200_simple.c.

It may be argued that this code should be moved somewhere else, but I
don't remeber to have seen any such review comments.

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@denx.de
You don't have to stay up nights to succeed; you have to  stay  awake
days.

  reply	other threads:[~2008-03-17 22:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24  7:35 Please pull linux-2.6-mpc52xx.git Grant Likely
     [not found] ` <47DE94F4.90804@semihalf.com>
2008-03-17 19:19   ` Grant Likely
2008-03-17 20:59     ` Wolfgang Denk
2008-03-17 21:43       ` Grant Likely
2008-03-17 22:28         ` Wolfgang Denk [this message]
2008-03-17 23:43           ` Grant Likely
2008-03-18  0:26             ` Wolfgang Denk
2008-03-18  2:42               ` Grant Likely
2008-03-18 12:20                 ` Josh Boyer
2008-03-18  8:29             ` Bartlomiej Sieka
2008-03-18 10:04               ` Richard Purdie
2008-03-25 15:29                 ` Bartlomiej Sieka
2008-03-18 14:47               ` Grant Likely
2008-03-18 16:41                 ` Richard Purdie
2008-03-18 16:53                   ` Grant Likely
2008-03-25 16:50                     ` Bartlomiej Sieka
2008-03-25 18:49                       ` Grant Likely
2008-03-25 17:38             ` Bartlomiej Sieka
2008-03-25 18:51               ` Grant Likely
2008-04-01 12:37                 ` Bartlomiej Sieka
2008-04-04 11:13                   ` Bartlomiej Sieka
2008-04-04 16:11                     ` Grant Likely
2008-04-04 16:14                       ` Grant Likely
2008-04-04 16:38                         ` Olof Johansson
2008-04-04 17:15                           ` Josh Boyer
2008-04-04 17:25                             ` Grant Likely
2008-04-15 10:34                       ` Bartlomiej Sieka
2008-03-18  7:57     ` Bartlomiej Sieka
  -- strict thread matches above, loose matches on Subject: below --
2009-01-09 23:09 Grant Likely
2008-11-14 19:20 Grant Likely
2008-11-24  3:38 ` Paul Mackerras
2008-11-24 14:41   ` Grant Likely
2008-05-01 18:04 Grant Likely
2008-04-29 13:34 Grant Likely
2007-10-16 23:22 Grant Likely
2007-10-17 10:27 ` Paul Mackerras
2007-10-17 13:13   ` Grant Likely
2007-10-10 16:30 Grant Likely
2007-10-11 17:35 ` tnt

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=20080317222836.AFA66241A2@gemini.denx.de \
    --to=wd@denx.de \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@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).