I can confirm that a few fixes in v2.1 were missing, so trunk works
correctly, didn't you forget to rebuild the kernel when building trunk ?
Attached is a patch to v2.1 that contain the fixes backported from
trunk. Please try this patch and tell me if this works for you.
In
Lionel Perrin wrote:
I can confirm that a few fixes in v2.1 were missing, so trunk works
correctly, didn't you forget to rebuild the kernel when building
trunk ?
Attached is a patch to v2.1 that contain the fixes backported from
trunk. Please try this patch and tell
Gilles Chanteperdrix a écrit :
Lionel Perrin wrote:
///* the following lines shouldn't be commented but xenomai... */
//else
//{
///* a new shm_file has been created, we need to truncate it
*/
//if (ftruncate(h_shm, nbvalues *
I can confirm that a few fixes in v2.1 were missing, so trunk works
correctly, didn't you forget to rebuild the kernel when building trunk ?
Attached is a patch to v2.1 that contain the fixes backported from
trunk. Please try this patch and tell me if this works for you.
In fact, I've
Lionel Perrin wrote:
I can confirm that a few fixes in v2.1 were missing, so trunk works
correctly, didn't you forget to rebuild the kernel when building trunk ?
Attached is a patch to v2.1 that contain the fixes backported from
trunk. Please try this patch and tell me if this works
- Will this shared memory be accessible to non rt-task ?
- What's the simplest way to share information with a non rt-task ?
Shared memory are also accessible to non-rt tasks. Since user-space
realtime and non-realtime threads from the same process reside in the
same address space, the
Lionel Perrin wrote:
- Will this shared memory be accessible to non rt-task ?
- What's the simplest way to share information with a non rt-task ?
Shared memory are also accessible to non-rt tasks. Since user-space
realtime and non-realtime threads from the same process reside
Lionel Perrin wrote:
- Will this shared memory be accessible to non rt-task ?
- What's the simplest way to share information with a non rt-task ?
Shared memory are also accessible to non-rt tasks. Since user-space
realtime and non-realtime threads from the same process reside
Lionel Perrin wrote:
Ok, thanks, i'll try. My old pc will have some job... :)
I still have a few questions :
- How can we load/unload posix skin ?
When configuring your kernel, configure the posix skin as a module. A
module xeno_posix.ko will then be compiled that you may load with
Hi,
I got some problems with shared memory.
I started from the shm_open example from opengroup.org.
When I compile it as non real time tasks, it works properly. But since I
tried to compile it with
gcc $(xeno-config --posix-cflags) shm_open.c $(xeno-config
--posix-ldflags) -o xeno_shm_open,
i
Lionel Perrin wrote:
Hi,
I got some problems with shared memory.
I started from the shm_open example from opengroup.org.
When I compile it as non real time tasks, it works properly. But since I
tried to compile it with
gcc $(xeno-config --posix-cflags) shm_open.c $(xeno-config
11 matches
Mail list logo
