Rockbox Development > Starting Development and Compiling

Pointers are killing me...Help needed.

<< < (3/4) > >>

saratoga:
Some 5Gs have 32MB, others have 64MB.  Theres also 96k of zero cycle IRAM.  CPU is by PP and I think runs at 60 or 75MHz.  They're 2x ARM7TDMI cores.  See here:

http://www.ipodlinux.org/PP5020

Sentertainment:
I haven't done too much C, mainly a bit of C++....anyways, I was sure there had to be some way.
I've found a method for it, but not exactly the same as in C++

http://www-ee.eng.hawaii.edu/~tep/EE160/Book/chap14/subsection2.1.2.2.html
http://www.cs.cf.ac.uk/Dave/C/node11.html
http://www.fftw.org/fftw3_doc/Dynamic-Arrays-in-C.html

bluebrother:
The method you mentioned uses malloc. While it is possible to do this using dynamic memory Rockbox doesn't have malloc. This has been discussed over and over again (also in a thread of you), and malloc / dynamic memory isn't wanted in Rockbox. Which means this methods don't help for coding Rockbox.

Speaking of plain C, I'm pretty sure quite some of the people posting on this thread earlier would have mentioned malloc.

lowlight:
You can fake dynamic memory allocation in plugins by using plugin_get_buffer (to use the remainder of the plugin buffer) or plugin_get_audio_buffer (to use the larger playback buffer, but stop playback).

GodEater:
I'm assuming that the plugin_get_buffer() and plugin_get_audio_buffer() calls return only the one pointer to the start of that area of memory though? It's not like calling malloc() where you get a new pointer to the next bit of free memory each time ?

Navigation

[0] Message Index

[#] Next page

[*] Previous page