forums.ps2dev.org

had the same problem on fedora 9 when increasing the timeout value no problem anymore thx jsharrad

on the psp i have start psplink V3.0 on the pc i start USBHOSTFS /home/f731/myhomebrew on the pc i start pspsh [f731@localhost pspsh]$ ./pspsh host0:/> debug psp_pdf.prx PSPLink USB GDBServer (c) 2k7 TyRaNiD host0:/> Loaded host0:/psp_pdf.prx - UID 0x042B945D, Entry 0x088040AC as said in the tutoria...

yep at first sight it looks good. PSPSDK and my homebrews compiled and run without
problems so just see and wait

just updaded the script for 4.3.1 sorry ooPo i give you work i confirm the patch work
and i've just recompiled the pspsdk and my homebrews without problems

yes Heimdall i did because they are nor windows nor mingw related

the patch is provided int the tgz in the directory patch
just add include of stdlib and string.h so gcc >= 4.3 is happy ;)

I've just uploaded on http://194.7.150.2/psptoolchain431.tgz
a update of the toolchain for linux
gcc 4.3.1 and GDB 6.8

I've uploaded a upgrade of the psplibraries that correct a compilation problem
with gcc >= 4.3 for the libbulletml librarie

url : http://194.7.150.2/psplibraries.tgz

you are welcome; I didn't use the gcc 4.3.1 because i haven't find a official patch for it
the minpspw use for his build the patch of the version 4.3.0. The version 4.3.0 corrected for me a nasty bug when using many realloc

I've just uploaded on http://194.7.150.2/psptoolchain.tgz
a update of the toolchain for linux
gcc 4.3.0 and GDB 6.8

i have downloade gcc 4.3.0 patch with the patch found on the forum create a psp-build directory launch this script: #!/bin/sh LANGUAGES="c,c++" CFLAGS="-O2 -fomit-frame-pointer " \ BOOT_CFLAGS="-O2 -fomit-frame-pointer " \ BOOT_CXXFLAGS="-mthreads -fno-omit-frame-p...

Is there a upgrade of the toolchain.sh for linux available
that use the gcc 4.3.0 or gcc 4.3.1 as target cross compiler ?

Is there a plan to upgrade toolchain.sh to support gcc 4.3.1 for linux
windows has this with the minpspw

just a question when the pdf is in the folder where psppdf reside is it going down ? just to see if it is in the filechooser functon or in the sumatrapdf. Currently there is a bug when the xref of the pdf is > than 2^32 it crash and return to the xmb i try to fix this for preview 3. As said before i...

try it ;) currently i'm profiling the reader
i have also provide the source so ... if you have a problem fix a give me a feedback

pspdf is using the last sumatra pdf library so suport the last features of adobe pdf format (aka acrobat 9). look at the speed when the image is rendered (currently the proces to create the bimap is greater than bookr i'm working on it) but when the bitmap is created there is no comparaison when you...

I've juste release the preview 2 of my pdf reader binary : http://www.enterinmydream.info/~sauronlenoir/psppdf.zip source: http://www.enterinmydream.info/~sauronlenoir/psppdf_src.zip What's new: icon on xmb blink message on the splash screen flechooser RC1 written from scatch rendering dropped suppo...

a nice tuto and sample for inline asm with gcc for psp
http://www.psp-programming.com/forums/i ... ?topic=935

raphael you again you are omnipresent on the psp scene (joke)
thx for the link

int test(int couleur) { int c; __asm__ ( ".set push\n" ".set noreorder\n" "lv.s s000,%1\n" "mfv %0, s000\n" ".set pop\n" : "=&r"(c) : "m"(couleur) ); return (c); } this function just return the param couleur as the function re...

yes and no i must load the structure of the pdf a bunch of pointers but it is done once the idea of 2 thread is i load the page asked and when this page is ready the main thread display it and ican navigate into the bitmap created. The cache server continue to prefetch page -1 and page +1 int the ho...

thx as read in previous discussions the multi tasking iof psp s cooperatif and not preemptif are all the api involve by this ? if i pool for a system event or a message box does my main thread have cpu i'm currently written a cache server for my pdf reader the idea behind is start 2 threads. One han...

repons to my question int the sdk folder in the samples there are samples
of messagebox ec ..
But the question about the heap and a thread and his private stack remains

i saw in the sdk this semaid = sceKernelCreateSema("MyMutex", 0, 1, 1, 0); * * @param name - Specifies the name of the sema * @param attr - Sema attribute flags (normally set to 0) * @param initVal - Sema initial value * @param maxVal - Sema maximum value * @param option - Sema options (no...

when creating a new thread with sceKernelCreateThread there is a initial stack that you can give.as param doest the newly created thread use this stack for malloc or does it use the global heap space of the homebrew determine by the PSP_HEAP_SIZE_KB(-256); Is there a IPC (inter process communication...

here is the makefile and the hello source adapted. Makefile: TARGET = hello OBJS = module.o main.o CFLAGS = -O2 -G0 -Wall CXXFLAGS = $(CFLAGS) -fno-exceptions -fno-rtti ASFLAGS = $(CFLAGS) LIBDIR = LIBS = -lgphobos -lm -lpspsdkD LDFLAGS = EXTRA_TARGETS = EBOOT.PBP PSP_EBOOT_TITLE = Hello World PSPSD...

gcc patched and D compiled without problem but when generating libpspsdkA.o i have the following error with the makefile provide ../../../libphobos/internal/cmain.d:5: référence indéfinie vers « _Dmain » ../../../libphobos/internal/cmain.d:5: référence indéfinie vers « _Dmain » is this the main entr...

here is my drawing function void draw_psp(int pagenum,float drawzoom) { fz_error *error; fz_matrix ctm; fz_irect bbox; fz_pixmap *pix; char *dst_ptr; char *src_ptr; int i,xx,yy,w, h, bh; triImage* bitmap_page = 0; int page_courante; int old_page_courante; triFloat x = 0.f, y = 0.f; triVec2 *pStick,o...

try the tri library it's a very cool library
use svn to checkout here is the url to the site

http://trac2.assembla.com/openTRI

thx raphael but a zoom at 1.7 is very good the pdf is readable on the psp
by te way where did you found all the documentation about programming
the gu

agree but gcc is by essence a compiler design to run on different architecture so
some compilation flag wil generated overhead or even worse runtime errors