Re: [MiNT] fVDI TTF issues

[Frank Naumann <fnaumann@mail.CS.Uni-Magdeburg.De>]

Hello!

> Well, but the pipe handling is also done via the syscalls right? I've
> tried to look into the XaAES handler for this, but I still don't
> understand that perfectly. I know the pipe can be created before the
> interrupt handler is installed, but what about the later communication? I
> can't see a way :(. Sorry, but I'm still not that experienced in FreeMiNT
> kernel coding.

Can you explain what do you mean with 'interrupt handling'? Or do you just
mean the normal system call servicing?

> ? I actually thought that all VDI functions are happening during in an
> interrupt handler since the API is done via the trap instruction...
> Could you explain if I'm wrong?

The trap#X are not interrupt request. This are traps, also called system
calls.

The difference: interrupts happen asynchronous; normally comming from
I/O devices; traps happen synchronous, called from processes. From the
technical handling this is a big, big difference.

> I would guess that the kernel itself should have the complete VFS
> abstraction accessible for its internals. Frank? Others?

Sure, yes :-)

> I'm loading the fVDI from the rc.local script. But it is usable even if
> you execute it before in the AUTO folder (this is done in afros - see the
> ARAnyM downloads for more details).

I don't think this is the right way.

> I would rather assume to get fVDI into the kernel space as soon as we can.

Yes, that's the best (also an parallel version for TOS/MagiC should be no
problem; the differences are small I think).


Ciao
   ...Frank

--
ATARI FALCON 040 // MILAN 060
-----------------------------------------
http://www.cs.uni-magdeburg.de/~fnaumann/
e-Mail: fnaumann@freemint.de