linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jan Neskudla <jan.neskudla.ext@nsn.com>
To: ext Gerhard Jaeger <g.jaeger@sysgo.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/5] rapidio: adding memory mapping IO support and misc fixes
Date: Fri, 08 May 2009 13:39:12 +0200	[thread overview]
Message-ID: <1241782752.16400.41.camel@demuxf9c> (raw)
In-Reply-To: <200905081228.10955.g.jaeger@sysgo.com>

Hi Gerhard, 

Yes I am sure, I know I chosen a different board than I use. I wanted to
show that this compilation problem is not influenced by our e500
patches. So I did the test on the pristine 2.6.29.1 kernel without any
external patches applied, and the problem is exactly the same when the
rionet is compiled for E500 with our patches. 

And anyway the dma_client structure is defined in the 2.6.28, but not in
the 2.6.29, so it looks to me that a rionet dma support is written for
older kernel. 

Here is the Linus tree and async_tx tree merge tree months ago
and info is:
 dmaengine: kill struct dma_client and supporting infrastructure

http://git.kernel.org/?
p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9e8a3a5b8298a3c814ed37ac5756e6f67b6be41

                     Jan 

On Fri, 2009-05-08 at 12:28 +0200, ext Gerhard Jaeger wrote:
> Hi Jan,
> 
> On Friday 08 May 2009 12:06:35 Jan Neskudla wrote:
> [SNIPSNAP]
> > Important CONFIG options are: 
> > PPC_86xx=y
> > HPC8641_HPCN=y
> 
> you're using a e500 board (EP8548A), but the options above
> will be used when building a kernel for a e600 machine (MPC8641).
> Are you sure that is okay?
> 
> - Gerhard

  reply	other threads:[~2009-05-08 11:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 14:10 [PATCH 0/5] rapidio: adding memory mapping IO support and misc fixes Jan Neskudla
2009-05-07 15:21 ` Kumar Gala
2009-05-08 10:06   ` Jan Neskudla
2009-05-08 10:28     ` Gerhard Jaeger
2009-05-08 11:39       ` Jan Neskudla [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-28 10:16 Li Yang
2009-04-28 12:06 ` 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=1241782752.16400.41.camel@demuxf9c \
    --to=jan.neskudla.ext@nsn.com \
    --cc=g.jaeger@sysgo.com \
    --cc=linuxppc-dev@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).