Author Topic: VoodooPS2 update  (Read 33846 times)

0 Members and 1 Guest are viewing this topic.

andyvand

  • VoodooLabs
  • Posts: 51
VoodooPS2 update
« on: April 15, 2009, 09:05:16 PM »
I've recently updated VoodooPS2 sources.
Enjoy everybody...
It also is right now 1 big project instead of 6 smaller ones...
You can get the sources and binaries from following URL:

[Moderator]
Download URL has been removed. Please do not post modifications of an active project's source on our forum. If you would like to be a part of it you are welcome to join the project and submit your changes through the normal channels. Forks of projects are not a good thing =)
[/Moderator]
« Last Edit: April 15, 2009, 10:00:46 PM by sckevyn »

lebidou

  • Resident
  • Posts: 133
Re: VoodooPS2 update
« Reply #1 on: April 15, 2009, 09:16:55 PM »
What have you changed ?

andyvand

  • VoodooLabs
  • Posts: 51
Re: VoodooPS2 update
« Reply #2 on: April 15, 2009, 09:22:52 PM »
What have you changed ?
I integrated everything into a single xcode project and I've replace the IOSyncer::create function (which is deprecated) by a new function and fixed some minor warnings (also commented out the #warning part with an #if 0...)

noeyesee1

  • Entrant
  • Posts: 9
Re: VoodooPS2 update
« Reply #3 on: April 16, 2009, 06:43:04 AM »

Where can I download this update?

Kabyl

  • VoodooLabs
  • Posts: 158
Re: VoodooPS2 update
« Reply #4 on: April 16, 2009, 12:20:48 PM »

Where can I download this update?
Please read the comment left by the moderator.
There is nothing for end users to see here, plus it's not an "update" (wrong title).

andyvand

  • VoodooLabs
  • Posts: 51
VoodooPS2 Update Patch
« Reply #5 on: April 16, 2009, 06:18:54 PM »
At general request I've made a new patch in diff type of format along with a little shell script.
Put the files under the VoodooPS2Controller-0.98 folder and run dopatch.sh
For those not having the latest kernel headers and stuff in path you can use the little installer of my kernel build tools for having a better build environment (also with latest libkmod.a and libkmodc++.a).
It will generate better results...
Get it from:
http://rapidshare.com/files/222173821/AnV_Kbuild.zip
« Last Edit: April 16, 2009, 10:04:12 PM by andyvand »

mackerintel

  • VoodooLabs
  • Posts: 38
Re: VoodooPS2 Update Patch
« Reply #6 on: April 17, 2009, 12:06:33 AM »
At general request I've made a new patch in diff type of format along with a little shell script.
Don't include diffs to project files they spam anything useful out and make patch impossible to review.
- uint32_t interrupts[2] = { 0x01, 0x0c };   // PS2 interrupts
+ uint32_t interrupts[2] __attribute__((__unused__)) = { 0x01, 0x0c };   // PS2 interrupts
Do you consider this a proper fix?

andyvand

  • VoodooLabs
  • Posts: 51
Re: VoodooPS2 update
« Reply #7 on: April 17, 2009, 12:22:03 AM »
No not really but I'll get to that...
BTW: since I modded the projects under 1 big one how else am I supposed to do the diffs...

Kabyl

  • VoodooLabs
  • Posts: 158
Re: VoodooPS2 update
« Reply #8 on: April 17, 2009, 12:38:17 AM »
No not really but I'll get to that...
BTW: since I modded the projects under 1 big one how else am I supposed to do the diffs...
Just exclude the user config files under the "<Project>.xcodeproj/" when you create a diff (usually only "project.pbxproj" is needed).

mackerintel

  • VoodooLabs
  • Posts: 38
Re: VoodooPS2 update
« Reply #9 on: April 17, 2009, 12:40:14 AM »
No not really but I'll get to that...
Please don't remove warnings with unproper fixes. It defeats the very purpose of warning
Quote
BTW: since I modded the projects under 1 big one how else am I supposed to do the diffs...
Just remove -N option from your diff command - you didn't create any useful files. Also look "man diff"

sckevyn

  • VoodooLabs
  • Posts: 29
Re: VoodooPS2 update
« Reply #10 on: April 17, 2009, 12:57:10 AM »
Well that would be a design goal now wouldn't it....

You see why winging things on your own is a bad idea? =) The projects were setup separately so that it would be easy to debug and track any issues. Now that you threw the whole thing into one bag, have fun trying to track down where it broke...

As a goal for a programmer it makes no sense to have everything stuffed into one bin... the end user doesn't care because they are only interested in the end output, which are kexts... not the method the kext gets generated.

Long term there will be a standalone installer, but for now while there is still active development, the source project is available for people who want to tinker. But re-arranging the entire development environment is not an effective use of programming time. Fixing bugs and new features that is the goal.. Make it pretty after things work =)

It's nice that you wanted to change how it looks for someone to compile but honestly that's make busy work. it doesn't change the functionality of the project or the experience for the end user.

We're not catering to programmers or people who want to play with source code, and you shouldn't either. The goal is an improved working PS2 driver.

sckevyn

No not really but I'll get to that...
BTW: since I modded the projects under 1 big one how else am I supposed to do the diffs...
Just exclude the user config files under the "<Project>.xcodeproj/" when you create a diff (usually only "project.pbxproj" is needed).
« Last Edit: April 17, 2009, 01:00:45 AM by sckevyn »

andyvand

  • VoodooLabs
  • Posts: 51
Re: VoodooPS2 update
« Reply #11 on: April 17, 2009, 01:01:30 AM »
Really??? you really think that having 6 separate projects is easier?
Debugging like this is just as easy...
And I have right now only one thing to say:
THIS IS THE LAST TIME I'VE CONTRIBUTED TO THE VOODOO PROJECT!
If all of you guys think you know everything better I tend to say do it yourself... there is nothing productive coming from arguments like everybody is giving...
DO WHATEVER YOU WANT!
* arrogance has never helped anybody... *

Kabyl

  • VoodooLabs
  • Posts: 158
Re: VoodooPS2 update
« Reply #12 on: April 17, 2009, 01:20:29 AM »
Really??? you really think that having 6 separate projects is easier?
Debugging like this is just as easy...
And I have right now only one thing to say:
THIS IS THE LAST TIME I'VE CONTRIBUTED TO THE VOODOO PROJECT!
If all of you guys think you know everything better I tend to say do it yourself... there is nothing productive coming from arguments like everybody is giving...
DO WHATEVER YOU WANT!
* arrogance has never helped anybody... *

Actually I've never seen any contribution from you to the Voodoo projects, and this was your first serious attempt.

If you got the impression that we think we know everything better, then I have to say; you lack respect, you don't welcome advices, and have no experience (or even the common sense) in contributing to projects, and working in groups.

We're all here to have fun and learn from each other, isn't that your main motivation? unfortunately, you made me believe otherwise.

Good luck.
« Last Edit: April 17, 2009, 01:22:04 AM by Kabyl »

joemulder

  • Entrant
  • Posts: 4
Re: VoodooPS2 update
« Reply #13 on: April 18, 2009, 07:29:25 AM »
please don't flight
I hate to see skilled people not to work well together due to lack of teamwork skills.

please read the following:

STAGES OF TEAM PERFORMANCE
(Drexler/Sibbet Team Performance Model)

FORMING ACCORDING TO OPERATIONAL OBJECTIVES

1.   Orientation      Why am I here? - What is my/our purpose?
                        
            Critical Elements:
            Engaging in strategic planning.
            Stable clear, unique scope, and mandate for this team.
            Having a “big picture” template.
                        
2.   Trust Building      Who are you?
            Why are you part of this team?
            What will be my role and status?

            Critical Elements:
            Knowing clearly what is each member’s expertise
            and role/responsibility.
            Maintain a warm and positive curious attitude.
            Having mechanisms in place to address inter-
            personal issues as they arise.
            Reward all information sharing.

STORMING BASED ON INFORMATION GLEANED DURING FORMING AND BASED ON OPERATIONAL OBJECTIVES

3.   Goal/Role      How do our roles and status mix?
   Clarification      How do we efficiently together meet the objectives?

            Critical Elements:
            Knowing that goals shift.
            Letting everyone know clearly of goal/role changes.
            Clearly explaining the rationale for goal definition
            and role assignment.
            Clearly understanding where one person starts and
            the other leaves off in any process.

NORMING

4.   Commitment      What will be our work habits? Norms? Usual practices?

            Critical elements:
Be watchful for the evolution of negative norms, place them on the table early and work them through by applying a behaviourally anchored action plan.
            Recognize positive norms and celebrate them in order to                      keep them alive.      

PERFORMING

5.   Implementation   Systematically plan on how to meet the objectives on                      time.

            Critical Elements:
            Team leadership style.
            Having appropriate stable procedures.
            Ensure that objectives are realistic.
            Ongoing tracking of progress.
            Informing all parties of the progress as it happens.
            A priori plan on how you will solve potential barriers to                      success.
            Engage in creative thinking.

6.   High         Synergy - working in unison to meet the objectives.
   Performance   
            Critical Elements:
            Ensure that different languages and professional                         orientation definitions are clarified.
            Ensure that resources are adequately provided.
            Ensure recognition of work by clientele.
            Ensure ongoing professional development of personnel.
            Prioritization in times of overload.
            Ensure value-added differentiation from other groups.
                        
DEFORMING

7.   Renewal      Celebration of leaving members.
            Learn from ended projects/assignments.

            Critical Elements:
            Feedback.
            Document the learnings for next time.
            Take the time to grieve and celebrate.
            Face to face renewal is more rewarding - do an offsite.
            Explicitly link outcome to original objectives.

« Last Edit: April 18, 2009, 07:33:02 AM by joemulder »

Kabyl

  • VoodooLabs
  • Posts: 158
Re: VoodooPS2 update
« Reply #14 on: April 18, 2009, 11:43:27 AM »
please don't flight
I hate to see skilled people not to work well together due to lack of teamwork skills.

please read the following:

STAGES OF TEAM PERFORMANCE
(Drexler/Sibbet Team Performance Model)
...

Thanks for the post, but.. it's really not about teamwork skills, it's about the personal attitudes then about the personal skills :) and then comes teamwork skills.