From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Wolfgang Denk" <wd@denx.de>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Please pull linux-2.6-mpc52xx.git
Date: Mon, 17 Mar 2008 15:43:43 -0600 [thread overview]
Message-ID: <fa686aa40803171443q7a53f0balbb49740116c6552@mail.gmail.com> (raw)
In-Reply-To: <20080317205956.BAC85241A2@gemini.denx.de>
On Mon, Mar 17, 2008 at 2:59 PM, Wolfgang Denk <wd@denx.de> wrote:
> In message <fa686aa40803171219s7135a0f8n91bcd20329a94637@mail.gmail.com> you wrote:
> >
> > > What is the status of the various MPC5200-related patches (support for
> > > TQM5200, CM5200 and Motion-PRO boards, few drivers, etc) posted some
> > > time ago by Marian Balakowicz? There's been some comments to the patches
> > > on the list, which were addressed and no further discussion occurred, so
> > > we were hoping that the changes would go upstream (in 2.6.25). I can see
> > > that the .dts files for those boards are in the mainline already, but I
> > > see no trace of for example _defconfig files -- could you shed some
> > > light on this?
> >
> > Yes, the separate dts files have been dropped in preference for a
> > single mpc5200_defconfig for all 5200 boards.
>
> I know that my opinion doesn't matter but that's a stupid thing to
^^^^^^^^^^^^^^^^^^^^^^^^^
Bull. You know better than that.
> do. Do you think that this single mpc5200_defconfig will (a) work and
> (b) be useful on all 5200 boards? Who hast tested it, and on which
> platforms?
a) the same way we know that 5200 ethernet driver (for example) works
on all 5200 boards. If it breaks for one board then we fix it.
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.
> And what about the other patches? I see no code for these boards in
> arch/powerpc/platforms/52xx/ ?
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.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-03-17 21:43 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 [this message]
2008-03-17 22:28 ` Wolfgang Denk
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=fa686aa40803171443q7a53f0balbb49740116c6552@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--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).