Squidge
Certified Guru
< Removed on request from Mr. Mirko >
> Here's the SDK I'm currently working with for ArmADS. It's a derivative work of MirkosSDK071. I can't really call it a port, because it's not compatible with his.
Huhhh, 95% copy+paste, yehh a derivative work...
1) why are you not creating a compatible port ?
I think the coderz want somthing compatibel, so they
can try ads and gcc compiler on the same source.
2) if youre not satified with some of my code, or think you can improve
something, why not talk to me, iam always open for suggestions.
3) changing line:
u16 gp_ButtonResult(void) {
to
u16 gp_ButtonResult(void)
{
and putting a big
// Modified 04/05/04 Squidge
over the file. Is really a big modification...
You got my permission to use my stuff, in the hope we result in a
compatibel SDK for linux/windows_gcc/windows_ads ...
Iam a little disapointed...
Why are you getting so rought...Squidge posted on May 8 2004 at 08:43 PM said:Personally, I thought that it was enough to leave your credits in all the files so people knew where it come from, and then state clearly on my post that it was based on your SDK. However, since you don't like this idea, I'll remove it from the site.
I would like to know however how much of it is actually your own work. The chatboard source code is mainly from Mr Spiv, I wouldn't be suprised if you pulled 95% of grafik.c from somewhere else considering how similar it is to other code on the web, gp_irq.S is so similar to other pd code it's scary. DMA routines are in abundance, SMFS is simply the Samsung source code from Darkfaders website, and Zlib is also public domain.
The means that the main code you have probably written yourself is just the button code, font code, sbox, sound & sprite (and of course the examples & documentation). Is this true? I'd just like to know so I remove the offending files and routines.
>I'm not getting rough, just asking a question about what files you wrote, so I can delete them from my sdk and rewrite. Thanks for the answer.Squidge posted on May 8 2004 at 10:14 PM said:I'm not getting rough, just asking a question about what files you wrote, so I can delete them from my sdk and rewrite. Thanks for the answer.
"why you dont want to work with me together, creating a compatible SDK for gcc and ads ?"
Because what you want is not what I want. From your code I can clearly see we have totally different coding styles, thoughts about how things should work, and what things should be in a SDK. I'm not interested in chatboard, sprites, timers and sound routines, which is why I left them out (I prefer to do things like that on a per-project basis). I didn't like the way your dma routines worked, so I changed them. I changed the rest of your routines to more closely match my coding style. It took me almost 2 days to convert your SDK over to ADS because of the way the code was written, the lack of prototypes, assuming the user was using GCC, etc. Working together is just not going to work out, therefore it would be best if we went different ways from now on, and not use any of each others code.
> As for the LCD registers, I did have the find the values by myself, as the code you have in grafik.c is wrong and doesn't work properly. The only reason it works to a degree is because the bios already sets up most of the registers for you.Squidge posted on May 8 2004 at 11:44 PM said:I don't remember removing comments. I never said your code was so bad, just not in my style.
As for the LCD registers, I did have the find the values by myself, as the code you have in grafik.c is wrong and doesn't work properly. The only reason it works to a degree is because the bios already sets up most of the registers for you.
Yes, there is a prototype file, but not all functions are present in it. Some functions assume return types and parameters in your code. I added prototypes for them and placed them into the prototypes file.
I can and do work with other coders (it's actually part of my job at work), but some people, like yourself, I just can't work with.
I did ask Mirko if I could port a version of his SDK to ADS. Whilst I didn't mention that it wouldn't be full port, I did at least ask first. After changing a few things, I decided best not to keep the original name.
No, I'm not still looking at your source code, that was when I couldn't get my program working correctly, and found the fault to be in your SDK. I fixed the fault and carried on.mr.mirko posted on May 9 2004 at 01:08 AM said:> As for the LCD registers, I did have the find the values by myself, as the code you have in grafik.c is wrong and doesn't work properly. The only reason it works to a degree is because the bios already sets up most of the registers for you.Squidge posted on May 8 2004 at 11:44 PM said:I don't remember removing comments. I never said your code was so bad, just not in my style.
As for the LCD registers, I did have the find the values by myself, as the code you have in grafik.c is wrong and doesn't work properly. The only reason it works to a degree is because the bios already sets up most of the registers for you.
Yes, there is a prototype file, but not all functions are present in it. Some functions assume return types and parameters in your code. I added prototypes for them and placed them into the prototypes file.
I can and do work with other coders (it's actually part of my job at work), but some people, like yourself, I just can't work with.
I did ask Mirko if I could port a version of his SDK to ADS. Whilst I didn't mention that it wouldn't be full port, I did at least ask first. After changing a few things, I decided best not to keep the original name.
Ohh, there is no bios on my gp32, surprise surprise, it works very vell.
If youre sutch a good coder, its of couse no problem for you solving all bugs, and "keep them secret for you"... But hey, how did you find out all is wrong ? Are you still looking at my source ? Are you not starting at the beginning ? ( printing out the arm9.pdf ) ?
I can also tell you that the cpu setting is a litte wrong, i corrected it in my next release, and did i mention, that i will not tell you, what is wrong there...