From: Christian Kujau <evil@g-house.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Sven Hartge <hartge@ds9.gnuu.de>,
linux-kernel@vger.kernel.org,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.6.5-pre* does not boot on my PReP PPC
Date: Mon, 05 Apr 2004 23:19:12 +0200 [thread overview]
Message-ID: <4071CD50.2000402@g-house.de> (raw)
In-Reply-To: <20040405155022.GL31152@smtp.west.cox.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[ if someone is bored from me cc'ing too many - plz cry! ]
Tom Rini wrote:
| OK, hmm. I've got some better ideas then. It sounds like the code to
| have puts show up on VGA isn't selected/compiled in. Or, there's still
| some other problem wrt the OF transition code. Just having a serial
| console selected still doesn't give output however, right?
I'll give it a try with 2.6 this week.
|
|>another issue here: i was finally able to cross-compile 2.5.x / 2.6.x
|>kernels (on x86). i tried to compile kernels from 2.5.21 on with
|>"allnoconfig" (was introduced in 2.5.21). only 2.5.30 can be built, all
|>other attempts to build "zImage" fail...(still compiling 2.5.6x)...
|>(full logs of builds available...)
|
| The simple answer is, don't use allnoconfig :). Do a 'make
| common_defconfig' and then from there turn off stuff you don't need.
um, yes. but the target "common_defconfig" was disabled somewhere in
2.5, so my shini script broke. i wanted to do common_defconfig first,
then always keep my .config and do "oldconfig" after patching, but
somehow my script broke, so i went with "allnoconfig"...but ok, i'll try
again.
if anyone is interested: http://nerdbynature.de/bits/sheep/build/
all the logfiles produced when patchin/compiling 2.5.21 up to 2.5.75.
right here the latest 2.4-benh and 2.6-benh kernels (via rsync), also
compiled via crosscompile: http://nerdbynature.de/bits/sheep/latest-kernel/
thanks,
Christian.
- --
BOFH excuse #212:
Of course it doesn't work. We've performed a software upgrade.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAcc1Q+A7rjkF8z0wRAtxBAKCrbpGe3/HlW8UMLAdFKHCnWiyB/QCfV4FC
hVoNM7pW01ntTdFBETVxT44=
=jCF2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-04-05 21:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 18:33 2.6.5-pre* does not boot on my PReP PPC Meelis Roos
2004-03-26 18:51 ` Tom Rini
2004-03-27 13:55 ` Sven Hartge
2004-03-29 15:09 ` Tom Rini
2004-03-29 15:15 ` Tom Rini
2004-03-30 11:31 ` Meelis Roos
2004-03-30 18:45 ` Sven Hartge
2004-04-04 17:34 ` Christian Kujau
2004-04-05 15:50 ` Tom Rini
2004-04-05 21:19 ` Christian Kujau [this message]
2004-04-05 21:48 ` Hollis Blanchard
2004-04-05 22:30 ` Hollis Blanchard
2004-04-05 21:45 ` Christian Kujau
2004-04-05 16:15 ` Tom Rini
2004-03-30 18:49 ` Sven Hartge
2004-03-30 19:09 ` Tom Rini
2004-03-26 21:54 ` Christian Kujau
2004-03-27 13:56 ` Sven Hartge
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=4071CD50.2000402@g-house.de \
--to=evil@g-house.de \
--cc=hartge@ds9.gnuu.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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