From: SIP COP 009 <sipcop009@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: 8272ADS and Linux 2.6.12
Date: Wed, 13 Jul 2005 23:55:49 -0700 [thread overview]
Message-ID: <5a4792c0050713235574522cfb@mail.gmail.com> (raw)
Hello,
We have a MPC8272 Eval Board which came with Linux 2.4 and U-boot. We
wanted to move to 2.6. I downloaded the latest 2.6.12 sources and
compiled the sources for this platform. The kernel is built, have run
the mkimage tool, but the kernel wont boot. It just hangs after
decompressing the image.
Any ideas ? Anything different that needs to be done for 2.6 ? Or any
known issues ?
Thanks!
ashutosh
next reply other threads:[~2005-07-14 7:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 6:55 SIP COP 009 [this message]
2005-07-14 13:25 ` 8272ADS and Linux 2.6.12 Kumar Gala
2005-07-14 19:05 ` SIP COP 009
2005-07-15 3:05 ` Allen Curtis
2005-07-15 3:11 ` Allen Curtis
2005-07-15 14:14 ` SIP COP 009
2005-07-15 15:29 ` Allen Curtis
2005-07-17 6:52 ` Mike Rapoport
2005-07-19 17:18 ` SIP COP 009
2005-08-19 16:42 ` Matthew McClintock
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=5a4792c0050713235574522cfb@mail.gmail.com \
--to=sipcop009@gmail.com \
--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).