Re: [MiNT] fVDI TTF issues

[Standa Opichal <opichals@seznam.cz>]

Hi!

On Fri, 20 Jun 2003, Frank Naumann wrote:

> Hello!
> 
> > Is there some way how to make the system calls use a specific process
> > context?
> 
> A system call is per definition executed in the current process context.

Understood.

> > I need to call the freetype from the wrapper application context
> > despite the fact that it is hapenning in the interrupt handler (VDI call).
> 
> You can't use system calls at all from interrupts. Only specific kernel
> routines are interrupt safe and can be used from interrupt handlers.

Yes, I know, but I didn't find other way of how to use FreeType except 
porting it completely to kernel space.

> > If this is not feasible then I can see only one way: Port the engine as a
> > kernel module.
> 
> I don't think this is a big problem. FreeType is already designed in mind
> of portability and use only some simple ANSI-C functions for I/O, or I'm
> wrong?

I don't know what does it use in details, but I guess that you are right. 
It has also pluggable allocators so that the port should not be a big 
problem.
BTW: What I/O functions should I use from within the kernel module so that 
they would perform in the kernel context itself?

The other problem is that I will need to wait for the fvdi.prg to be 
initialized before I hook the VDI vector. I'll probably need to hook a 
fake interrupt which will check the fVDI cookie presece and if true then 
unhook and hook the regular font handling hook as in front of the fVDI 
hook in the XBRA chain. Does anyone you see some other way?

BTW: Johan, I would like to see the fVDI as a kernel module and gcc 
compilable. Do you think there is a chace to get this in acceptable time 
frame?

best regards

STan