From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Felix Radensky <felix@embedded-sol.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Accessing PCI-E resources on 460EX
Date: Tue, 02 Dec 2008 08:04:12 +1100 [thread overview]
Message-ID: <1228165452.7356.123.camel@pasglop> (raw)
In-Reply-To: <4933C5AF.5040406@embedded-sol.com>
On Mon, 2008-12-01 at 13:08 +0200, Felix Radensky wrote:
> and I'm afraid it can take me some time to move from 2.6.26 to 2.6.28.
> Any chance I can backport you modifications to 2.6.26 ? Have you
> modified
> other files except arch/powerpc/sysdev/ppc4xx_pci.c to fix these
> problems ?
>
Yes, quite a few changes in the PCI layer etc...
Board support changes shouldn't be too hard to port over tho, it depends
how you did them.
Cheers,
Ben.
next prev parent reply other threads:[~2008-12-01 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 21:09 Accessing PCI-E resources on 460EX Felix Radensky
2008-11-03 21:31 ` Ayman El-Khashab
2008-11-03 22:53 ` Felix Radensky
2008-11-04 18:40 ` Henry Bausley
2008-12-01 7:54 ` Benjamin Herrenschmidt
2008-12-01 11:08 ` Felix Radensky
2008-12-01 21:04 ` Benjamin Herrenschmidt [this message]
2008-12-02 22:38 ` Felix Radensky
2008-12-04 9:22 ` Felix Radensky
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=1228165452.7356.123.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=felix@embedded-sol.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).