Re: [ft-devel] porting freetype to Texas DSP C55x

[david turner]

Peter M a écrit :

I have successfully compiled the freetype 2.1.8 engine on Code Composer 2.21 but I expiriance some memory problems.

The problem seems to be with the malloc, free, realloc  functions.To solve the issues there must be used the TI specific

functions:

 

-----------------------------------------------------------------------------------------------------------------------------------------

Syntax:                   addr = MEM_alloc(segid, size, align);

 

Parameters:            Int            segid;      /* memory segment identifier */ 

            Uns             size;        /* block size in MADUs */ 

            Uns             align;       /* block alignment */

 

Return Value:         Void        *addr;      /* address of allocated block of memory */

-----------------------------------------------------------------------------------------------------------------------------------------

Syntax:                   status = MEM_free(segid, addr, size);

 

Parameters:            Int            segid;      /* memory segment identifier */ 

            Ptr               addr;       /* block address pointer */ 

            Uns             size;        /* block length in MADUs*/

 

Return Value:         Bool         status;     /* TRUE if successful */

-----------------------------------------------------------------------------------------------------------------------------------------

Syntax:                   MEM_redefine(segid, base, length);

Parameters:            Int            segid;      /* segment to redefine */ 

            Ptr               base;       /* base address of new block */ 

            Uns             length;     /* length (in MADUs) of new block */

 

Return Value:         Void

-----------------------------------------------------------------------------------------------------------------------------------------

 

 

My questions are:

- Doze someone use freetype on a Texas c55x platform?

I really don't know.

- How match RAM dose it use?

It really depends on the font being used, some configuration options, and even
the version of the font engine you're using. Better test it yourself.

- How to rewrite or change the memory object to make it work?

 

for an embedded system, the easiest way is to modify the file src/base/ftsystem.c
you should be able to use the "user" field of the FT_Memory object to store your
segment id. the work would be to:

- change "ft_alloc", "ft_realloc" and "ft_free" to use the TI functions
- change "FT_New_Memory" to allocate the initial FT_Memory object
  either statically, or with the TI functions as well.

Hope this helps,

- David Turner
- The FreeType Project  (www.freetype.org)

 

Tanks in advance

 Peter

_______________________________________________
Freetype-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/freetype-devel
  

***********************************************************************************
Information contained in this email message is confidential and may be privileged, and is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the address@hidden and destroy the original message.
***********************************************************************************