From: David Jander <david.jander@protonic•nl>
To: linuxppc-embedded <linuxppc-embedded@ozlabs•org>
Subject: Trouble with 2.6.16 on ppc8xx ?
Date: Fri, 14 Apr 2006 10:50:56 +0200 [thread overview]
Message-ID: <200604141050.56757.david.jander@protonic.nl> (raw)
Hi all,
I just cg-update'd to the HEAD of the denx 2.6.x kernel tree (2.6.16 as
released).
Our board-support stuff was succesfully moved along from 2.6.14 (when
everything but the SCC3 and SCC4 uarts worked just fine).
I compiled a kernel without any special drivers, just console on ttyCPM0, but
after "Uncompressing Kernel Image ... OK" there is no more output and no
further activity on ethernet (it should boot from nfs-root) or any other
device.
After "cg-seek DENX-v2.6.15; make clean uImage", it works again (everything
seems fine, system boots).
Our board is based on a MPC852T and until now we used "MPC86X" as the
BOARD_CHIP_NAME and it worked just fine with 2.6.14 and 2.6.15, but not with
2.6.16 as described above.
When doing "cg-diff" and carfully examining it's output, I can only see our
board-support stuff (not very much, not very special) and some custom drivers
that are disabled anyway.
Any clue about where to start looking?
I didn't find any suspicious changes in arch/ppc/mm, arch/ppc/syslib and
arch/ppc/kernel. Neither in drivers/serial/cpm_uart.
Which change from 2.6.15 to 2.6.16 could have broken 8xx support for us?
Is there perhaps a known issue with 2.6.16 and ppc8xx I am unaware of?
Greetings,
--
David Jander
next reply other threads:[~2006-04-14 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 8:50 David Jander [this message]
2006-04-17 21:52 ` Trouble with 2.6.16 on ppc8xx ? Marcelo Tosatti
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=200604141050.56757.david.jander@protonic.nl \
--to=david.jander@protonic$(echo .)nl \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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