From: Jon Loeliger <jdl@freescale.com>
To: joachim.bader@diehl-aerospace.de
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Help: Kernel BUG with U-boot 1.1.4 and kernel 2.6.23 scanning PCIe on a MPC8641D board
Date: Tue, 22 Jul 2008 11:57:05 -0500 [thread overview]
Message-ID: <48861161.8050707@freescale.com> (raw)
In-Reply-To: <OFB15FD6AA.EA941C67-ONC125748E.00488CEE-C125748E.004A8A08@diehl-gruppe.de>
joachim.bader@diehl-aerospace.de wrote:
>
> Hello folks,
>
> we run a proprietary board with Freescale MPC8641D using U-boot 1.1.4
> and Linux kernel 2.6.23
>
> I read in the logs some messages that 2.6.23 does contain some bugs
> related to PCIe
Correct.
> and it would be a good choice to upgrade to 2.6.25. Is
> this one of that cases?
Almost certainly. You should pick up top of tree if you can.
> Currently we would like to prevent switching the kernel version.
You could back-port the PCIe bug fixes and rewrite if you wanted.
My guess is that a _trial_ run of the current top of tree,
or at least 2.6.26 might Just Work and fix your issues.
It would be less work to try it than do discover-n-back-port...
jdl
prev parent reply other threads:[~2008-07-22 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 13:33 Help: Kernel BUG with U-boot 1.1.4 and kernel 2.6.23 scanning PCIe on a MPC8641D board joachim.bader
2008-07-22 16:57 ` Jon Loeliger [this message]
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=48861161.8050707@freescale.com \
--to=jdl@freescale.com \
--cc=joachim.bader@diehl-aerospace.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).