From: Tom Rini <trini@kernel.crashing.org>
To: okorpil@fh-landshut.de
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Serial Console / Booting Linux with the PPCbug on MVME2100?
Date: Thu, 1 Apr 2004 08:09:43 -0700 [thread overview]
Message-ID: <20040401150943.GE21709@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0404011015410.476@ppcproject1>
On Thu, Apr 01, 2004 at 10:26:28AM +0200, okorpil@fh-landshut.de wrote:
> Hello!
>
> I'm using a plain vanilla 2.4.25 kernel with the attached config.
>
> As you may have noted I'm using the zImage.prep.
>
> Do I need to make a mkbugboot by hand? (It's only configured to be done
> for the CONFIG_LOPEC, CONFIG_PPLUS and CONFIG_PRPMC750)
This is what I expected. Looking quickly over the prep_* files in
arch/ppc/platform confirms that the MVME2100 is not supported by these
files. As an aside, mkbugboot is only needed to put an image into flash
and boot it. mkprep is used for hd(/cd?), floppy and network.
Now, a quick googling for Linux and MVME2100 gives this very old, but
mostly sufficient patch:
http://www.aps.anl.gov/asd/people/anj/mvme2100.patch.gz
Since you have the hardware, from here it should be not too hard, using
the LoPEC as an example, port the code in that patch to 2.4 and 2.6 (if
you do a patch vs 2.6 we can get that support into kernel.org, if you're
willing to try and keep the platform working).
-
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-01 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 12:08 Serial Console / Booting Linux with the PPCbug on MVME2100? okorpil
2004-03-31 17:09 ` Tom Rini
2004-04-01 8:26 ` okorpil
2004-04-01 15:09 ` Tom Rini [this message]
2004-04-01 15:53 ` Oliver Korpilla
2004-04-01 8:45 ` okorpil
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 10:55 okorpil
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=20040401150943.GE21709@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=okorpil@fh-landshut.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).