Skip to: Site menu | Main content


Welcome to PSP-Programming.com, a place for developers to get together.

Welcome to the forums. Here you can find other user tutorials as well as homebrew releases and the source code repository. You can also ask for help with your code here and post your own homebrew!

PSP-Programming.com Forums
February 04, 2012, 10:18:47 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length

News: Join our IRC channel: ##psp-programming on freenode
Home Help Search Shop Login Register
Digg This!
Pages: [1]
Print
Author Topic: Nid resolver  (Read 2397 times)
sauron_le_noir
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4
471.42 points

View Inventory
Send Money to sauron_le_noir

View Profile
« on: November 14, 2008, 09:34:22 AM »

Can someone explain me how the nid resolver work on a CF. If i want to code a ASM program on the psp
does the CF automaticly map function like pspDebugScreenPrintf to the right  entry  or must i per version
of CF found the nids bymyself? Sorry i'm very new on mips asm. I was in another live a OS/2 device driver develloper
and just for the fun i want to program a homebrew in ASM. I have see that sony often  changed his nids
of his functions i have also heard about a nids resolver so that is the reason of my questions.
How to code in ASM a homebrew independant of the CF version. Is it be done at CF so you must not care
about nids ?

In the minifire sample written by TyRaNiD he use a file sysvcall1.h for firmware 1.O ans sysvcall15.h for firmware.h and for 4.xM33 or 5.xm33 what must we use?

Does someone have a hello world asm program that can be run on a kernel 5.xM33
« Last Edit: November 14, 2008, 10:27:29 AM by sauron_le_noir » Logged


macthefork
Newbie
*

Karma: +5/-0
Offline Offline

Posts: 22
721.82 points

View Inventory
Send Money to macthefork

View Profile
« Reply #1 on: November 15, 2008, 01:26:21 AM »

Unless you are going for a small footprint (like the minifire) which I probably wouldn't recommend you don't need to worry. Write your code in assembly and let the normal link step handle function imports. Looking at that small asm program it only uses the syscalls directly to remove the import structures which seriously bloat executable size.
Logged
Pages: [1]
Print
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 0.123 seconds with 25 queries.
Sister Sites: Guitar Hero 4   BrokeniTouch.com