From: Gerhard Jaeger <g.jaeger@sysgo.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Building a Kernel for the AMCC PPC440EP Bamboo Board
Date: Thu, 3 Mar 2005 09:23:22 +0100 [thread overview]
Message-ID: <200503030923.22677.g.jaeger@sysgo.com> (raw)
In-Reply-To: <20050302215308.GA6511@wohnheim.fh-wedel.de>
On Wednesday 02 March 2005 22:53, J=F6rn Engel wrote:
> On Tue, 1 March 2005 17:37:22 +0100, Gerhard Jaeger wrote:
> > On Tuesday 01 March 2005 17:14, Zeighami, Roy wrote:
> > >=20
> > > When I select 44x as the CPU type, I don't see "Bamboo" under machine
> > > type. =20
> >=20
> > This won't work, as Bamboo BSP stuff is currently not added.
>=20
> Correct.
>=20
> > > Any suggestions?
> >=20
> > try to use ebony_defconfig
>=20
> Doesn't work, neither does ocotea. Both are able to display "TUX!" on
> the dot-matrix display, but panic before writing any serial output.
>=20
> /me has one of these beauties as well and will try to hack up support
> for it. If anyone has patches or suggestions, help is always
> appreciated.
>=20
Could not confirm that so far! Ebony and Ocotea are working out of the
box, using these defconfig files! (pristine kernel 2.6.11)
Gerhard
=2D-=20
Gerhard Jaeger <gjaeger@sysgo.com> =20
SYSGO AG Embedded and Real-Time Software
www.sysgo.com | www.elinos.com | www.pikeos.com | www.osek.de=20
next prev parent reply other threads:[~2005-03-03 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 16:14 Building a Kernel for the AMCC PPC440EP Bamboo Board Zeighami, Roy
2005-03-01 16:37 ` Gerhard Jaeger
2005-03-02 21:53 ` Jörn Engel
2005-03-03 8:23 ` Gerhard Jaeger [this message]
2005-03-03 23:05 ` Jörn Engel
2005-03-04 7:17 ` Gerhard Jaeger
2005-03-04 15:39 ` Matt Porter
2005-03-04 16:06 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2005-03-02 7:51 Andriy Korud
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=200503030923.22677.g.jaeger@sysgo.com \
--to=g.jaeger@sysgo.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linuxppc-embedded@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).