From: Jon Loeliger <jdl@freescale.com>
To: Timur Tabi <timur@freescale.com>
Cc: Marco Stornelli <marco.stornelli@coritel.it>,
LinuxPPC-Embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: MPC8641D PCI-Express error
Date: Thu, 21 Feb 2008 09:26:13 -0600 [thread overview]
Message-ID: <47BD9815.9020002@freescale.com> (raw)
In-Reply-To: <47BD96F8.4090406@freescale.com>
Timur Tabi wrote:
> Marco Stornelli wrote:
>
>> No, it didn't. I have the same problem even with the 2.6.18 plus the
>> 2.6.24 PCI-Express code. I performed this action because I can't change
>> kernel version but I can modify it.
>
> Please try 2.6.24 (or even better, 2.6.25-rc2). You may have done something
> wrong in back-porting the code to 2.6.18. There's no reason why you can't at
> least try the latest version of the code for testing purposes, even if you can't
> use it in production.
>
Also, once you back-ported it and all the DTS changes, and all
the fsl_soc.c changes needed and , and, and otherwise made it
look _like_, 2.6.24 but still called it 2.6.18, after all that,
can you remind us what was the error or failure mode that you saw?
jdl
next prev parent reply other threads:[~2008-02-21 15:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 16:13 MPC8641D PCI-Express error Marco Stornelli
2008-02-21 2:20 ` Kumar Gala
2008-02-21 8:02 ` Marco Stornelli
2008-02-21 15:21 ` Timur Tabi
2008-02-21 15:26 ` Jon Loeliger [this message]
2008-02-21 15:37 ` Marco Stornelli
2008-02-21 15:58 ` Jon Loeliger
2008-02-22 13:52 ` Marco Stornelli
-- strict thread matches above, loose matches on Subject: below --
2008-02-29 8:50 Marco Stornelli
2008-02-19 9:06 Marco Stornelli
2008-02-19 14:19 ` Jon Loeliger
2008-02-19 15:42 ` Marco Stornelli
2008-02-19 16:06 ` Jon Loeliger
2008-02-19 16:43 ` Marco Stornelli
2008-02-19 16:59 ` Jon Loeliger
2008-02-19 20:19 ` Kumar Gala
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=47BD9815.9020002@freescale.com \
--to=jdl@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=marco.stornelli@coritel.it \
--cc=timur@freescale.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.