180 replies to this topic

[tacchan23]

Chainfire, on Nov 3 2009, 18:51, said:

I know it's still very techy and weird, but I hope it clears it up a bit.

It did for me:)

[NuShrike]

It's the difference between a i386, and an i386 + i387.  Hope that helps.. ;-)

[vodanhdaisu]

Thank you Chainfire, i've already understood. But still a little bit confusing, according to you, enabling FPU enhances and speeds up performing in calculations, how about other aspects like video encoding, playback, browsing web, photos on the device? is it enhanced ?

[NuShrike]

vodanhdaisu, on Nov 3 2009, 21:18, said:

But still a little bit confusing, according to you, enabling FPU enhances and speeds up performing in calculations, how about other aspects like video encoding, playback, browsing web, photos on the device? is it enhanced ?

I've already explained this in post #10.

[Albertri]

NuShrike, on Nov 5 2009, 07:10, said:

I've already explained this in post #10.

NUShrike will FPU enabler this would this help if we are using the TF3D 1.3 CFC? sorry to ask such noob question I am not a developer nor expert these things

[NuShrike]

Albertri, on Nov 4 2009, 17:46, said:

NUShrike will FPU enabler this would this help if we are using the TF3D 1.3 CFC? sorry to ask such noob question I am not a developer nor expert these things

The FPU enabler definitely helps the OpenGL ES graphics in TF3D because most of the driver code (GK and Samsung) uses float numbers instead of another number optimization shortcut.

Once I get there, the matrix math in GK's libgles_cm will be improved also which should help with more GL graphics speed.

[Albertri]

NuShrike, on Nov 5 2009, 09:03, said:

The FPU enabler definitely helps the OpenGL ES graphics in TF3D because most of the driver code (GK and Samsung) uses float numbers instead of another number optimization shortcut.

Once I get there, the matrix math in GK's libgles_cm will be improved also which should help with more GL graphics speed.

Cool tks for the info when I install TF3D 1.3 I have not enable or run the FPU enabler program. must re install the TF3D 1.3 again with FPU enabler see if there's a noticeable difference.


Cheers

[Albertri]

Oh an one last thing will you guys release a cab for FPU enabler? rightnow it's manual or you'll need to run it everytime. Or this is really just a proof of concept?

cheers

[Chainfire]

Well, the thread title does say it's a proof of concept doesn't?

Rest assured we are still working on improving this. Have some patience. If you had any idea how complicated this hack is, you wouldn't be asking in the first place.

[Albertri]

Chainfire, on Nov 5 2009, 10:24, said:

Well, the thread title does say it's a proof of concept doesn't?

Rest assured we are still working on improving this. Have some patience. If you had any idea how complicated this hack is, you wouldn't be asking in the first place.

cool tks we all know you guys are doing this FOC and we sure it's not easy. I've been following your threads closely and I know what you guys are doing is really huge thing to all O2 users like me we really appriciate it.

[NetRipper]

FYI, results on the Leo/HD2:

25 functions were unpatched, only divs/addd/subd/muld/divd were kept patched. Others had an average of like 60%. "divd" improved by 411%, and the 4 others by 150%.

SKtools before patch:
Integer:  805.9
Floating: 19.5

SKtools after patch:
Integer: 812.6
Floating: 55.2

It's hard to see if it improves anything in everyday apps with a 1GHz cpu FPSEce (ps emu) might be a good candicate to try with, but waiting for their 1.0 release first...

[NuShrike]

NetRipper, on Nov 14 2009, 14:13, said:

FYI, results on the Leo/HD2:
25 functions were unpatched, only divs/addd/subd/muld/divd were kept patched. Others had an average of like 60%. "divd" improved by 411%, and the 4 others by 150%.

Thanks for the interesting stats.  Sounds like Qualcomm didn't improve the FPU to keep up in throughput with the Integer in the Snapdragon.  Even the "slow" S3C6410 @ 533MHz reaches the same FPU throughput in the SKTools test!

Due to lacking kernel support by any WinMob ODM, the way we implement also robs the FPU 2x full-native speed anyways.  Can't directly support NEON either because there's no public documentation on it.

Status: partial driver has been implemented, but there's still some work for feature parity with FPUenabler.  No visuals as a driver so a separate app will be needed to give that.

Edited by NuShrike, 19 November 2009 - 08:00 PM.

[naTpuoT87]

NuShrike Hi! Is it possible to do autopatch in Fpu Enabler?

[Chainfire]

You are not reading. We are working on a driver. Once that is finished, all you have to do is install the CAB and not worry about it ever again

[bluhound]

NuShrike, on Nov 20 2009, 03:52, said:

Thanks for the interesting stats.  Sounds like Qualcomm didn't improve the FPU to keep up in throughput with the Integer in the Snapdragon.  Even the "slow" S3C6410 @ 533MHz reaches the same FPU throughput in the SKTools test!

Due to lacking kernel support by any WinMob ODM, the way we implement also robs the FPU 2x full-native speed anyways.  Can't directly support NEON either because there's no public documentation on it.

Status: partial driver has been implemented, but there's still some work for feature parity with FPUenabler.  No visuals as a driver so a separate app will be needed to give that.

Just being curious, what does 'feature parity' mean?

[Ganhiru]

Hi Chainfire,

I'm still using v0.70 of your pachter, I read a lot of comics on my device and with the FPU calls pachted the time needed to load a page has decreased as well. Also some games ( like Tower Defence ) seem to run just that bit smoother.
So ty for the work so far.

Edited by Ganhiru, 01 December 2009 - 02:45 PM.

[dwallersv]

rumkokos, on Oct 3 2009, 03:08, said:

Yeah they are doing a great job indeed! However what is the point of having 3D in spb 3.5? I've seen it on HTC TP2 and its no use at all. If thats related to any other useful 3D app its ok but if its only for spb 3d carosel view its no point indeveloping that as its useless.. eye candy only

I constantly shake my head at responses like this.

Some people like Death Metal (a genre of music). I think it sounds like incomprehensible screaming and noise, akin to 40 people scratching their fingernails on blackboards.

Does that make people who like DM fools with bizarre taste in music? Only to the small-minded.

Asthetic taste is a personal, and utterly subjective thing. There is no good/bad in any universal sense.

Such it is with "eye candy", or from the perspective of someone that values it, "really cool graphical features". Such is the case with the 3D effects in MS3.5, and I'd bet money there are enough users out there that think it's awesome and are willing to select MS3.5 over shells with similar functionality (i.e. not the presentation asthetics) that SPB decided this was well worth the development investment.

Proof is in all the people posting on their forums about the devices that DON'T support the UI feature -- as well as a healthy number here.

You don't think it matters, hence it is "eye candy" to you. No problem. You might give some thought, though, to respecting other people's differing perspectives and values in regard to this sort of thing. It would expand your understanding.

[dwallersv]

NuShrike, on Nov 3 2009, 11:15, said:

It's the difference between a i386, and an i386 + i387. Hope that helps.. ;-)

That's likely complete gibberish to anyone under 35!

[dwallersv]

bluhound, on Nov 20 2009, 07:25, said:

Just being curious, what does 'feature parity' mean?

Means has the same feature set as the other.

For example, the current app-based implentation has a UI to control the thing. A driver can't do that (it's "headless"). So, some interfaces into the driver need to be added that can be accessed by an external application to implement the same capability to control the patch (i.e. turn it "on" and "off"). Absent this, there's no way to control the state of the patch with a driver alone.

By anology, consider WiFi. The underlying software that makes it all work is in a driver module. However, without the user apps in windows to control wifi, you wouldn't be able to search for and select networks, configure them, turn wifi on and off, etc. There'd be no way to interact with the low-level software that drives the hardware.

This is the same thing.

[bluhound]

dwallersv, on Dec 4 2009, 05:25, said:

Means has the same feature set as the other.

For example, the current app-based implentation has a UI to control the thing. A driver can't do that (it's "headless"). So, some interfaces into the driver need to be added that can be accessed by an external application to implement the same capability to control the patch (i.e. turn it "on" and "off"). Absent this, there's no way to control the state of the patch with a driver alone.

By anology, consider WiFi. The underlying software that makes it all work is in a driver module. However, without the user apps in windows to control wifi, you wouldn't be able to search for and select networks, configure them, turn wifi on and off, etc. There'd be no way to interact with the low-level software that drives the hardware.

This is the same thing.

Now I understand.  Thanks!