From: Matt Porter <mporter@kernel.crashing.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Linux-2.6.9-rc2 kernel build for mvme5100
Date: Wed, 22 Sep 2004 09:47:56 -0700 [thread overview]
Message-ID: <20040922094755.A19612@home.com> (raw)
In-Reply-To: <20040922163309.GL16619@smtp.west.cox.net>; from trini@kernel.crashing.org on Wed, Sep 22, 2004 at 09:33:09AM -0700
On Wed, Sep 22, 2004 at 09:33:09AM -0700, Tom Rini wrote:
> On Tue, Sep 21, 2004 at 08:55:41AM +1000, David Gardiner wrote:
>
> > Okay I took a different way, looking at the code and having lots of
> > problems trying to get it to compile and the similarity between the
> > PowerPlus series I compiled a pplus kernel with the default config and
> > the patch above and it booted, yeah, and dumped bits to the console, on
> > an mvme2604.
> >
> > So I made some changes Kconfig so that MVME5100 and PPLUS were basically
> > the same ( The architecture for the 5100 and pplus are similar, so why
> > was the code separated? arrgh I'm about to be burnt to a crisp, but if
> > we don't get our fingers burnt we never learn) which the patch for is
> > attached. This patch also allows the selection of nvram which I want
> > also and it seems to compile no matter what you select, which it didn't
> > before. And so selecting MVME5100 it booted and dumped bits to the
> > console, yeah.
>
> I _think_ the answer is simply that the mvme5100 work predated the
> CONFIG_PPLUS work. If you can come up with a patch that adds mvme5100
> support to CONFIG_PPLUS, we can get rid of the MVME5100-specific stuff.
> (And, if you do, please look at Documentation/SubmittingPatches and the
> Developers Certificate of Origin).
This is true. When Randy Vinson did the CONFIG_PPLUS work, he decided
to initially just gather up all the boards that were covered (in a
suboptimal fashion) under PReP. The idea was to bring the other
standalone boards into CONFIG_PPLUS in the future, but nobody has
gotten around to it...until now, apparently.
-Matt
next prev parent reply other threads:[~2004-09-22 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 4:29 Linux-2.6.9-rc2 kernel build for mvme5100 David Gardiner
2004-09-16 5:36 ` Matt Porter
2004-09-16 7:54 ` David Gardiner
2004-09-20 17:32 ` Tom Rini
2004-09-20 19:23 ` Matt Porter
2004-09-20 22:55 ` David Gardiner
2004-09-21 0:12 ` David Gardiner
2004-09-22 16:33 ` Tom Rini
2004-09-22 16:47 ` Matt Porter [this message]
2004-09-23 20:14 ` David Gardiner
2004-09-21 9:15 ` Marius Groeger
2004-09-21 15:48 ` Tom Rini
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=20040922094755.A19612@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.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).