From: Scott Wood <scottwood@freescale.com>
To: Dan.Geer@faa.gov
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BSE-IP
Date: Tue, 26 Jan 2010 15:03:44 -0600 [thread overview]
Message-ID: <4B5F58B0.9090401@freescale.com> (raw)
In-Reply-To: <OF3B9B44C2.CF12E7DB-ON852576B7.0070B35D-852576B7.0070B371@faa.gov>
Dan.Geer@faa.gov wrote:
> My end goal is to run the latest 2.6.32 kernel on an ancient BSE-IP MPC823
> board. One step in the process is an attempt to compile the last "working"
> kernel for this platform, and it hasn't been pretty.
>
> Back in 2005, Kumar Gala caught an issue with compiling for this platform,
> and Dan Malek commented about which options to choose to complete a
> successful compile. I'm in the process of trying to get that (2.6.16.62)
> series to work. It seems that one of the newer dev boards got the focus of
> the port, and the BSE-IP drop out of sight.
Newer boards have been used for recent development, but it shouldn't be
too hard to get other boards to work. With the device tree, a lot more
of the hardware description is done in a data structure, rather than
scattered throughout code.
I'd start by taking one of the existing supported 8xx boards in the
current tree, and adapting its device tree and platform file to describe
the BSE-IP, using the old code as a reference. You may also need
bootwrapper changes, depending on what firmware you use.
Things have changed enough that I don't recommend trying to directly
merge the old code into the new kernel.
-Scott
next prev parent reply other threads:[~2010-01-26 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 20:30 BSE-IP Dan.Geer
2010-01-26 21:03 ` Scott Wood [this message]
2010-01-26 22:04 ` BSE-IP Dan.Geer
2010-01-26 22:17 ` BSE-IP Scott Wood
2010-01-26 23:28 ` BSE-IP Dan.Geer
-- strict thread matches above, loose matches on Subject: below --
2010-02-01 18:08 BSE-IP Dan.Geer
2010-02-01 18:24 ` BSE-IP Scott Wood
2010-02-01 18:59 ` BSE-IP Dan.Geer
2010-02-01 19:06 ` BSE-IP Scott Wood
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=4B5F58B0.9090401@freescale.com \
--to=scottwood@freescale.com \
--cc=Dan.Geer@faa.gov \
--cc=linuxppc-dev@lists.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).