From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Daniel Jacques (Alten)" <jacques.daniel@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] rt_heap and DMA32 zone
Date: Wed, 13 Oct 2010 14:36:45 +0200 [thread overview]
Message-ID: <4CB5A7DD.9090203@domain.hid> (raw)
In-Reply-To: <DF9F3A3C150B0646A17FF1487C1B6D5E0380C010@domain.hid>
Daniel Jacques (Alten) wrote:
> Please find bellow and in attachment the requested information:
>
> Linux kernel: 2.6.32.15
> Adeos patch: adeos-ipipe-2.6.32.15-x86-2.7-01.patch
> Xenomai: 2.5.4
> Host Linux distribution: Based on Debian 5.0
> Compiler: gcc version 4.3.2
>
> Piece of code:
> #define HEAP_SIZE_IN_BYTES 16*1024*1024
> static int __init audioInit_module(void)
> {
> int status;
> RT_HEAP heap;
>
> ...
>
> /* Create the global heap */
> if( (status = rt_heap_create(&heap, "audioInputHeap", HEAP_SIZE_IN_BYTES, H_SHARED|H_DMA )) < 0 )
> {
> printk("rt_heap_create audioInputHeap error %d\n", status );
> return status;
> }
> else
> {
> printk ("Heap audioInputHeap created\n");
> }
>
> ...
>
> }
So, if I understand correctly, the problem is that Linux does not use
the DMA32 pool when it is passed the GFP_DMA flag? In that case, you
probably need an H_DMA32 flag, which get translated into GFP_DMA32 by
the rtheap code.
--
Gilles.
next prev parent reply other threads:[~2010-10-13 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DF9F3A3C150B0646A17FF1487C1B6D5E0380C00C@rennsmail06.eu.thmulti.com>
2010-10-13 7:58 ` [Xenomai-help] rt_heap and DMA32 zone Daniel Jacques (Alten)
2010-10-13 9:36 ` Gilles Chanteperdrix
2010-10-13 10:07 ` Daniel Jacques (Alten)
2010-10-13 12:36 ` Gilles Chanteperdrix [this message]
2010-10-13 13:51 ` Daniel Jacques (Alten)
2010-10-13 14:07 ` Gilles Chanteperdrix
2010-10-13 14:18 ` Gilles Chanteperdrix
2010-10-13 14:31 ` Daniel Jacques (Alten)
2010-10-14 22:29 ` Gilles Chanteperdrix
2010-10-19 9:37 ` Daniel Jacques (Alten)
2010-10-19 10:22 ` Gilles Chanteperdrix
2010-10-19 10:52 ` Anders Blomdell
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=4CB5A7DD.9090203@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jacques.daniel@domain.hid \
--cc=xenomai@xenomai.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 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.