Re: [rtl] Shared Memory problem (the non-messy edition)

["Garth Gaddy" <Garth.Gaddy@ci.fresno.ca.us>]

Phil and Tomasz

Your advice on the munmap((void *) user_ptr, sizeof(SRAM_ACCESS)) worked great.

But as you both indicated, it would not solve my problem.  

Phil, I removed the memcpy statements from the Linux side code but still only get zeros on the Linux side when sending non-zero integers from the RT side.

I will keep digging, any suggestions appreciated.

Garth Gaddy


>>> Phil Wilshire <philwil@on-ramp.ior.com> 08/09/99 04:10PM >>>
Garth Gaddy wrote:
> 
> Phil
> 
> Kernel = 2.0.36
> 
> Lilo.conf has
>         append="mem=63m"
> at the bottom in a system with 64M
> 
> Both include files are listed.  Oops, it seems I listed <unistd.h> twice, would this cause a problem?

Try missing out the memcpy stuff ahd just manipulate the shared memory
directly from both sides.

I'll be gone to LinuxWorldExpo after tomorrow morning.
If you can try tonight I'll check mail last thing.

I have had good success with some of this stuff.

Phil Wilshire

>>> Tomasz Motylewski <motyl@stan.chemie.unibas.ch> 08/10/99 01:04AM >>>

> void free_sram (SRAM_ACCESS *user_ptr)
> {
>         munmap(user_ptr, sizeof(SRAM_ACCESS));
> }


Use munmap((void*) user_ptr, sizeof(SRAM_ACCESS));

to get rid of the warning. And do not expect it to solve your problem.

--
Tomek


--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail majordomo@rtlinux.cs.nmt.edu OR
echo "unsubscribe rtl <Your_email>" | mail majordomo@rtlinux.cs.nmt.edu
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/