Brandt Erickson wrote:
> > Ok, things get clearer. But why a kernel module? Are you *that* short on
> > CPU cycles?
>
> The reason why I'm trying to develop a kernel-space application is not for
> latency issues but because I need to be in kernel-space to read/write
> to/from my DAC.
There
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-confi
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-confi
> ioperm() or iopl() not applicable?
I'm not sure. I'm using a Sensoray S626 card (PCI). The driver I have is
something I pieced together from psuedo-working code I got from someone
else, so I'm not entirely sure how it works (or if it's even rt-safe).
-Brandt
_