yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] Shree_Jamdar:
Don't let this thread die!

Hey we need this man, im not gonna get a brand new fone with powerful gpu or a dual core tegra fone, im sure there are many people like me.
[Galaxy 3 Android Development] unreal3000:
yup....

i cant realy get a nnew phone cause i just got this one recently.........

and this is the case for most people!!

pls update us!

iv been checking ur progress page and it hasnt been updated for a while now!
[Galaxy 3 Android Development] tom3q:
I'm writing to inform you that the development is slowly, but actively ongoing behind the scenes, currently we are in process of adding FBO support.

Also there is some interest in this driver from people working on other systems based on s3c6410, so we might get some help in future.

As for Galaxy 3, I can't do any testing nor find any complete documentation for the s5p6442 chip, so the support is still not there, but it's just a matter of adjusting the kernel module appropriately (but you have to know how exactly, that's why some information is needed).
[Galaxy 3 Android Development] Benjamin_L:
This one is incomplete too?

http://www.spinics.net/lists/linux-samsung-soc/msg00703.html
[Galaxy 3 Android Development] Dharam_Maniar:
the problem is that there is no proper user manual on s5p6442 processor...

we refer to s3c6410 proc user manual only...

@tom3q: as you say, that FIMG 3DSE is same in g3 as it is in spica... so is it possible to try and use your driver in g3? and if it doesnt work, is there any chances of hardware becoming faulty?
[Galaxy 3 Android Development] tom3q:
I don't see MMIO base address of FIMG 3DSE registers defined there and this is the most important thing.

Breaking hardware isn't possible, but it is unlikely to work, because they have changed at least the base address and without knowing it the software won't be able to access the GPU. Same goes for IRQ number and also for memory area reserved for video data.
[Galaxy 3 Android Development] Dharam_Maniar:
well but some information can be found out from the current code of G3?
[Galaxy 3 Android Development] anant.0097:
yeah.... that's what i was wondering..... can the current drivers be broken down to reveal the base address and IRQ number........ it might be encrypted but is it possible to break it down?
[Galaxy 3 Android Development] unreal3000:
hey tom3q!

im still noob at kernel developing but i would love to be a tester!

pls do sign me up!

this is the only support i can give as of now but im trying my hand at kernel developing!
[Galaxy 3 Android Development] tom3q:
It's not even encrypted, it's a compiled binary which would have to be disassembled and partially reverse engineered. It's doable, of course, but my priority now is the S3C6410 platform and so I have other things to do.
[Galaxy 3 Android Development] anant.0097:
oh! i get it!....... but if someone does disassemble the binaries and is able to get the base address and irq then will it be possible to use the spica drivers on our phone? ...... if not then how much work will be done by obtaining the addresses?
[Galaxy 3 Android Development] unreal3000:
hey tom!!

could u pls give us a progress report?
[Galaxy 3 Android Development] Dharam_Maniar:
https://github.com/tom3q/openfimg/wiki/Status
[Galaxy 3 Android Development] unreal3000:
i already check the link buut i just wanted to know how tom3q's progress is going :D
[Galaxy 3 Android Development] hillbeast:
Basically, he seems to be working entirely on the Spica, and until that is finished, we can't get it on the G3. We've just got to be patient. So there is no progress on the G3 for now.
[Galaxy 3 Android Development] unreal3000:
kk tks! realy hope we can get this on the g3 once they get it o the spica...
[Galaxy 3 Android Development] hillbeast:
I was reading through dmesg for another purpose, and stumbled across these addresses. They're probably useless, but would they be of any help for the G3 port of the FIMG drivers?

<6>S3C JPEG Driver for S5P6442, (c) 2009 Samsung Electronics

<4>#### + s3c_jpeg_init ####

<4>#### s3c_jpeg_probe ####

<4>#### - s3c_jpeg_init ####

<6>S3C G3D Driver, (c) 2007-2009 Samsung Electronics

<4>s3c_g3d version : 0x1050300

<4>G3D_RESERVED_MEM_SIZE : 40 MB

<4>G3D_CHUNK_SIZE : 1 MB

<4>G3D_CHUNK_NUM : 40 (UI_CHUNK:6)

<4>0 th virt_addr = 0xe0800000, phy_addr = 0x40800000

<4>1 th virt_addr = 0xe0900000, phy_addr = 0x40900000

<4>2 th virt_addr = 0xe0a00000, phy_addr = 0x40a00000

<4>3 th virt_addr = 0xe0b00000, phy_addr = 0x40b00000

<4>4 th virt_addr = 0xe0c00000, phy_addr = 0x40c00000

<4>5 th virt_addr = 0xe0d00000, phy_addr = 0x40d00000

<4>6 th virt_addr = 0xe0e00000, phy_addr = 0x40e00000

<4>7 th virt_addr = 0xe0f00000, phy_addr = 0x40f00000

<4>8 th virt_addr = 0xe1000000, phy_addr = 0x41000000

<4>9 th virt_addr = 0xe1100000, phy_addr = 0x41100000

<4>10 th virt_addr = 0xe1200000, phy_addr = 0x41200000

<4>11 th virt_addr = 0xe1300000, phy_addr = 0x41300000

<4>12 th virt_addr = 0xe1400000, phy_addr = 0x41400000

<4>13 th virt_addr = 0xe1500000, phy_addr = 0x41500000

<4>14 th virt_addr = 0xe1600000, phy_addr = 0x41600000

<4>15 th virt_addr = 0xe1700000, phy_addr = 0x41700000

<4>16 th virt_addr = 0xe1800000, phy_addr = 0x41800000

<4>17 th virt_addr = 0xe1900000, phy_addr = 0x41900000

<4>18 th virt_addr = 0xe1a00000, phy_addr = 0x41a00000

<4>19 th virt_addr = 0xe1b00000, phy_addr = 0x41b00000

<4>20 th virt_addr = 0xe1c00000, phy_addr = 0x41c00000

<4>21 th virt_addr = 0xe1d00000, phy_addr = 0x41d00000

<4>22 th virt_addr = 0xe1e00000, phy_addr = 0x41e00000

<4>23 th virt_addr = 0xe1f00000, phy_addr = 0x41f00000

<4>24 th virt_addr = 0xe2000000, phy_addr = 0x42000000

<4>25 th virt_addr = 0xe2100000, phy_addr = 0x42100000

<4>26 th virt_addr = 0xe2200000, phy_addr = 0x42200000

<4>27 th virt_addr = 0xe2300000, phy_addr = 0x42300000

<4>28 th virt_addr = 0xe2400000, phy_addr = 0x42400000

<4>29 th virt_addr = 0xe2500000, phy_addr = 0x42500000

<4>30 th virt_addr = 0xe2600000, phy_addr = 0x42600000

<4>31 th virt_addr = 0xe2700000, phy_addr = 0x42700000

<4>32 th virt_addr = 0xe2800000, phy_addr = 0x42800000

<4>33 th virt_addr = 0xe2900000, phy_addr = 0x42900000

<4>34 th virt_addr = 0xe2a00000, phy_addr = 0x42a00000

<4>35 th virt_addr = 0xe2b00000, phy_addr = 0x42b00000

<4>36 th virt_addr = 0xe2c00000, phy_addr = 0x42c00000

<4>37 th virt_addr = 0xe2d00000, phy_addr = 0x42d00000

<4>38 th virt_addr = 0xe2e00000, phy_addr = 0x42e00000

<4>39 th virt_addr = 0xe2f00000, phy_addr = 0x42f00000

<4>[FSA9480] pm_check: pmic init finished

<1>##################### s5p_g2d_probe Success

<4> S5P6442 G2D Init : Done
[Galaxy 3 Android Development] darksyde18:
Wow!!

Great :)

I'll find people to back you up :D
[Galaxy 3 Android Development] tom3q:
It's not that I would have any problems taking all these values out of your existing libraries. Time is the problem here, I work primarily for Spica, which also needs a completely new kernel, because the software base is completely broken and this is the priority.

Also getting this running on i5800 is a good entry test for all people that could be interested in helping me. ;)

Oh, that would be great. Please keep me informed.
[Galaxy 3 Android Development] tom3q:
I need a dump of /system/lib/egl and /system/lib/libChunkAlloc.so from latest Froyo firmware of Galaxy 3.

Could anyone make one for me?
[Galaxy 3 Android Development] apollo5801:
Here is the egl folder.

http://www.megaupload.com/?d=PGECCY9C
[Galaxy 3 Android Development] tom3q:
Thanks. It turned out that I will also need /system/lib/libChunkAlloc.so. Do you mind getting it for me too?

Also, could you tell from what firmware version it is?
[Galaxy 3 Android Development] dhirend_6d:
Here you go. Latest firmware is JPS. :)
[Galaxy 3 Android Development] tom3q:
Well, here's my attempt to put together an instruction how to run OpenFIMG on Galaxy 3.

Latest version of my kernel module is universal and should work with any SoC with FIMG GPU, assuming that there is a proper platform device with resources defined in kernel (and from looking quickly at some kernel sources for G3 I believe it is). So just replace drivers/media/s5p6442/g3d_drv/s3c_g3d.c with my version of this file (https://github.com/tom3q/modules-new/tree/master/g3d) and the header, rebuild the kernel and you should be ready to go.

You will also need to modify your PMEM configuration.

In arch/arm/plat-s5p64xx/include/plat/reserved_mem.h you need to replace

#define RESERVED_PMEM_GPU1	(0 * 1024 * 1024)

with

#define RESERVED_PMEM_GPU1	(RESERVED_MEM_G3D)

and also replace

#define G3D_RESERVED_MEM_START (SKIA_RESERVED_PMEM_START - RESERVED_MEM_G3D)
#define G2D_RESERVED_MEM_START (G3D_RESERVED_MEM_START - RESERVED_MEM_G2D)
#define GPU1_RESERVED_PMEM_START (G2D_RESERVED_MEM_START - RESERVED_PMEM_GPU1)
#define RESERVED_PMEM_START (GPU1_RESERVED_PMEM_START - RESERVED_PMEM)

with

#define G3D_RESERVED_MEM_START (SKIA_RESERVED_PMEM_START - RESERVED_MEM_G3D)
#define G2D_RESERVED_MEM_START (G3D_RESERVED_MEM_START - RESERVED_MEM_G2D)
#define GPU1_RESERVED_PMEM_START (G3D_RESERVED_MEM_START)
#define RESERVED_PMEM_START (G2D_RESERVED_MEM_START - RESERVED_PMEM)

In arch/arm/plat-s5p64xx/devs.c remove the line

.no_allocator	= 1,

in

static struct android_pmem_platform_data pmem_gpu1_pdata = {
.name = "pmem_gpu1",
.no_allocator = 1,
.cached = 1,
.buffered = 1,
};

And this should be everything for the kernel.

You might also need to adjust /dev/s3c-g3d and /dev/pmem_gpu1 owner and permissions to system:graphics and 0666.

Let me know whether this works.

EDIT:

You will also need to change the clock name in my s3c-g3d.c from "3dse" to "g3d".
[Galaxy 3 Android Development] unreal3000:
tried but got this while making-

root@hell-pc:~/Desktop/g3/Kernel# make
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-arm
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
CC arch/arm/mach-s5p6442/mach-apollo.o
In file included from arch/arm/mach-s5p6442/mach-apollo.c:63:0:
arch/arm/plat-s5p64xx/include/plat/adcts.h:48:15: warning: useless storage class specifier in empty declaration
In file included from arch/arm/mach-s5p6442/mach-apollo.c:78:0:
arch/arm/plat-s5p64xx/include/plat/reserved_mem.h:50:6: warning: "G2D" is not defined
arch/arm/plat-s5p64xx/include/plat/reserved_mem.h:50:6: error: missing binary operator before token "RESERVED"
arch/arm/mach-s5p6442/mach-apollo.c:270:23: error: 'G2D' undeclared here (not in a function)
arch/arm/mach-s5p6442/mach-apollo.c:270:23: error: expected ')' before 'RESERVED'
arch/arm/mach-s5p6442/mach-apollo.c:658:5: warning: function declaration isn't a prototype
arch/arm/mach-s5p6442/mach-apollo.c: In function 'wlan_setup_power':
arch/arm/mach-s5p6442/mach-apollo.c:2765:31: warning: passing argument 2 of 's3c_config_gpio_alive_table' from incompatible pointer type
arch/arm/mach-s5p6442/mach-apollo.c:2698:6: note: expected 'int (*)[4]' but argument is of type 'unsigned int (*)[4]'
arch/arm/mach-s5p6442/mach-apollo.c:2766:31: warning: passing argument 2 of 's3c_config_gpio_alive_table' from incompatible pointer type
arch/arm/mach-s5p6442/mach-apollo.c:2698:6: note: expected 'int (*)[4]' but argument is of type 'unsigned int (*)[4]'
arch/arm/mach-s5p6442/mach-apollo.c:2809:31: warning: passing argument 2 of 's3c_config_gpio_alive_table' from incompatible pointer type
arch/arm/mach-s5p6442/mach-apollo.c:2698:6: note: expected 'int (*)[4]' but argument is of type 'unsigned int (*)[4]'
arch/arm/mach-s5p6442/mach-apollo.c: In function 'ldo38_control_by_usb':
arch/arm/mach-s5p6442/mach-apollo.c:1176:1: warning: control reaches end of non-void function
make[1]: *** [arch/arm/mach-s5p6442/mach-apollo.o] Error 1
make: *** [arch/arm/mach-s5p6442] Error 2
root@hell-pc:~/Desktop/g3/Kernel#

(just a stock kernel....no other modifications)

did all the changes too....

maybe somthing conflicting in mach-s5p6442?
[Galaxy 3 Android Development] cdesai:
It compiled with some changes you told and some more changes in the file dharam specified below

EDIT:

Same problem as dharam

I can see some part of the boot animation (stock one) but after that just the backlight stays on

Unable to get dmesg - adb not working
[Galaxy 3 Android Development] Dharam_Maniar:
I am getting error

drivers/media/s5p6442/g3d_drv/s3c_g3d.c: In function 's3c_g3d_unlock':
drivers/media/s5p6442/g3d_drv/s3c_g3d.c:213:2: error: implicit declaration of function 'pm_runtime_mark_last_busy'
drivers/media/s5p6442/g3d_drv/s3c_g3d.c:214:2: error: implicit declaration of function 'pm_runtime_put_autosuspend'
drivers/media/s5p6442/g3d_drv/s3c_g3d.c: In function 's3c_g3d_probe':
drivers/media/s5p6442/g3d_drv/s3c_g3d.c:421:2: error: implicit declaration of function 'pm_runtime_set_autosuspend_delay'
drivers/media/s5p6442/g3d_drv/s3c_g3d.c:422:2: error: implicit declaration of function 'pm_runtime_use_autosuspend'

looks like these functions are not defined for G3...

maybe you can tell me where they are defined for the spica, and i'll define them at the same position ?

EDIT:

OK, I got those functions in /include/linux/pm_runtime.h

I get a black screen at somepoint in the booting process...

the last i could take out from dmesg was

<4>!@beginofsystem_init1()
<6>s3cfb s3cfb.0: [fb1] video memory released
<6>s3c-fimc s3c-fimc.1: fimc_querycap: called
[Galaxy 3 Android Development] anujsh:
If this drivers are going to be working on spica for supporting gingerbread, then people working on CM7 should take this one seriously for porting it.
[Galaxy 3 Android Development] marcellusbe:
yes of course.... hopefully you are there to give us your advice...
[Galaxy 3 Android Development] anujsh:
seriously I am no one t advice anyone of u. like always hoping for the best to the g3 community.
[Galaxy 3 Android Development] mohitgalaxy3:
ha ha ha...LOL
[Galaxy 3 Android Development] Rapier07:
:d:d:d:d:d:d:d:d:d:d:d:d:d:d
[Galaxy 3 Android Development] tom3q:
This seems like you put a space (instead of "_") between G2D and RESERVED in line 50 of reserved_mem.h.
[Galaxy 3 Android Development] tom3q:
Well, I think it will be more reasonable to just remove any pm_runtime calls from the module as it's for domain gating on newer kernels and it seems yours is too old.

What about a logcat?
[Galaxy 3 Android Development] Dharam_Maniar:
removed pm_runtime call's and getting you logcat soon...

Edit: Here you go...Hope this helps :)

Complete logcat and dmesg before it freezes on black screen...

the backlight in on though...

Only cant access adb also..
[Galaxy 3 Android Development] tom3q:
Well, it doesn't surprise me that it crashes, since you try to run Samsung fimg libs with kernel module designed for OpenFIMG, which is incompatible (because being compatible with something broken by design would make it broken too).

You have to clone the OpenFIMG repo into vendor/ directory of your Android tree, compile it using make libGLES_fimg, remove Samsung fimg libs from /system/lib/egl and then put the compiled libGLES_fimg.so there.

EDIT: The line

<6>s3c-g3d s3c-g3d: detected FIMG-3DSE version 0.0.0

doesn't look good though. It makes me wonder if in your kernel you have the 3D domain disabled by default and so the chip stays powered off.

EDIT: Well, it seems you indeed do have. So, for a quick start, add

#include <plat/power_clk_gating.h>
#include <plat/s5p6442-dvfs.h>

to includes of the module and then

s5p6442_pwrgate_config(S5P6442_G3D_ID, S5P6442_ACTIVE_MODE);

to s3c_g3d_probe, preferably after

platform_set_drvdata(pdev, data);

This won't be especially power effective (well, it won't do any power management at all), but for testing it's enough.
[Galaxy 3 Android Development] Dharam_Maniar:
OK...will get back to you when done...marcellusbe can do it better...
[Galaxy 3 Android Development] tom3q:
Edited my previous post with information how to enable the domain.
[Galaxy 3 Android Development] Dharam_Maniar:
OK, did that

now it is

<6>s3c-g3d s3c-g3d: detected FIMG-3DSE version 1.5.3

but compiling the libGLES_fimg is still left...
[Galaxy 3 Android Development] tom3q:
OK. I will wait patiently, there is no hurry.
[Galaxy 3 Android Development] marcellusbe:
I will do it as soon as I get back home
[Galaxy 3 Android Development] Dharam_Maniar:
Getting an error. Using CM6.2 source.

target arm C++: libGLES_fimg <= vendor/libsgl/eglBase.cpp
vendor/libsgl/eglBase.cpp: In member function 'virtual EGLBoolean FGLWindowSurface::swapBuffers()':
vendor/libsgl/eglBase.cpp:1280: internal compiler error: in add_phi_arg, at tree-phinodes.c:395
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [out/target/product/apollo/obj/SHARED_LIBRARIES/libGLES_fimg_intermediates/eglBase.o] Error 1

maybe we should wait for marcellusbe to do it...
[Galaxy 3 Android Development] tom3q:
Well, this is a known GCC 4.4.0 bug. Remove const in line 1280 of eglBase.cpp and it should work.
[Galaxy 3 Android Development] Dharam_Maniar:
Well, if i remove the const copyBack it gives more errors..
[Galaxy 3 Android Development] tom3q:
To clarify my last post:

Replace

const Region copyBack(Region::subtract(oldDirtyRegion, dirtyRegion));

with

Region copyBack(Region::subtract(oldDirtyRegion, dirtyRegion));
[Galaxy 3 Android Development] Dharam_Maniar:
Ok, sorry my bad :p...trying it again... :)
[Galaxy 3 Android Development] Dharam_Maniar:
ok that solved it

now

vendor/libsgl/glesTex.cpp: In function 'void glEGLImageTargetTexture2DOES(GLenum, void*)':
vendor/libsgl/glesTex.cpp:1029: error: 'GL_BGRA_EXT' was not declared in this scope
make: *** [out/target/product/apollo/obj/SHARED_LIBRARIES/libGLES_fimg_intermediates/glesTex.o] Error 1

sorry to bug you ;)
[Galaxy 3 Android Development] tom3q:
Put this somewhere before the line that errors out:

#define GL_BGRA_EXT 0x80E1

No idea, why GL headers from Froyo don't have this defined.
[Galaxy 3 Android Development] Dharam_Maniar:
ok, i build them...now adding libGLES_fimg.so to /system/lib/egl

and other file required ?
[Galaxy 3 Android Development] tom3q:
I believe this file alone should be enough. Just remember to remove original Samsung libs from there.
[Galaxy 3 Android Development] Dharam_Maniar:
again stuck with black screen...

getting logcat and dmesg....
[Galaxy 3 Android Development] Panos_dm:
You said that you used cm6.2 source. Maybe I'm WAY too intolerant but should we expect an update.zip with the new libgles_fimg.so and a kernel with the new modules if everything works out well?

EDIT: I just saw that nothing changed..:(

sent from my CM6 nokia 3210
[Galaxy 3 Android Development] Dharam_Maniar:
Here you go...

Please wait and watch :)

Once it works, we shall do something...
[Galaxy 3 Android Development] tom3q:
Could you add

#define DEBUG

to s3c_g3d.c above all the includes?

This should make the kernel log a bit more verbose.
[Galaxy 3 Android Development] Dharam_Maniar:
OK doing that...
[Galaxy 3 Android Development] andreapier:
I'm sorry to interrupt your usefull discussion but i'd like to know if thise driver is getting compiled for android 2.2 or android 2.3... I cannot figure it out from the last messages... it seems to be 2.2 but i remember tom2q said in a previous post that it would be done for 2.3...

Am i missing something?
[Galaxy 3 Android Development] Dharam_Maniar:
Ok, now here is logcat and dmesg... after

#define DEBUG
[Galaxy 3 Android Development] tom3q:
It doesn't matter. It should work on any Android version. For Android 2.3 it's just a chance to get fully working hardware acceleration as Samsung FIMG libs don't work correctly on it.
[Galaxy 3 Android Development] tom3q:
Hmm, it makes no sense. Does it hang completely after printing "I/SurfaceFlinger( 3481): Client API: OpenGL ES" in the log or you can normally enter adb shell and execute some commands?
[Galaxy 3 Android Development] Dharam_Maniar:
it hangs completely...i cant enter adb shell...
[Galaxy 3 Android Development] tom3q:
What about trying to add

set_dvfs_doclk_level(0);

after

s5p6442_pwrgate_config(S5P6442_G3D_ID, S5P6442_ACTIVE_MODE);

in s3c_g3d.c?
[Galaxy 3 Android Development] Dharam_Maniar:
ok doing..2 mins...
[Galaxy 3 Android Development] Dharam_Maniar:
hangs after

I/SurfaceFlinger( 3493): Client API: OpenGL ES

same thing... :(
[Galaxy 3 Android Development] tom3q:
It seems that here ends my ability to debug things remotely. I can't say anything more without having access to the phone directly. This looks to me like invalid IO access or IRQ storm, nothing easy to debug.

You might try to comment the request_irq call in probe of s3c_g3d module, to check whether it isn't an IRQ storm.
[Galaxy 3 Android Development] Dharam_Maniar:
Ok, I'll try it out in sometime...going for dinner now :D

We should wait for marcellusbe to try it as well, he has better knowledge than me...so maybe some mistake by my end can be ruled out...
[Galaxy 3 Android Development] cdesai:
I wanted to try this (just to learn) so that we can get a second opinion (although dharam has a lot more knowledge and experience then me; and marcellusbe is simply great) but my net is broken and comp is having some issues so will try as soon as fixed - maybe we can use teamviewer to help you debug? - possible?)

You're doing great work man :D
[Galaxy 3 Android Development] dilzo:
So did you complete this on the Spica? If so were there any major improvements?
[Galaxy 3 Android Development] Dharam_Maniar:
Sadly that also doesnt work..

I think we should wait till marcellusbe gives it a try :)

Thank you for trying... Hopefully we may be able to get this working on G3... :)

Even i would like to know about dilzo's question? How much is the improvement on Spica for you ?
[Galaxy 3 Android Development] tom3q:
Well, improvements can't be measured yet. The project is still in development, it's far from being complete. At current stage it implements enough of OpenGL standard to run hardware accelerated Android on it, without Samsung proprietary binaries, with similar performance.

For more advanced applications, there are still many things to be added, lighting, palleted textures, software support for compressed textures unsupported by hardware, better memory management, low-level optimizations and even OpenGL ES 2.0 support, including a shader compiler, because currently only the fixed OpenGL ES 1.1 pipeline is supported (using precompiled emulation shader code blocks). And, of course, some bugs are yet to be fixed (or even found).

EDIT: Frame buffer objects are already implemented, but are waiting for me to merge them with my tree, so one thing less to implement.
[Galaxy 3 Android Development] Dharam_Maniar:
OK, thanks for the update :)
[Galaxy 3 Android Development] unreal3000:
wait are u saying that the 3d core isnt even used by default?
[Galaxy 3 Android Development] hillbeast:
No he made a mistake. It is enabled.
[Galaxy 3 Android Development] Dharam_Maniar:
I dont think it is a mistake, but in Spica it must be enabled by default, and for G3, it must be enabled in the driver...
[Galaxy 3 Android Development] tom3q:
Indeed, in original kernel of Spica they leave it enabled until the driver disables it for power saving when unused, so I assumed they did the same with G3, but it seems they fixed it.
[Galaxy 3 Android Development] mohitgalaxy3:
Marcellusbe are you still on the way, seems you went out to c ur GF............. :) :p:D

Just joking waiting for your reply on the ongoing implementation.
[Galaxy 3 Android Development] anujsh:
Please fellows, he is a hardworking guy, let him have a good sleep.
[Galaxy 3 Android Development] raja4sure:
Any Updates ?????
[Galaxy 3 Android Development] Blackyx007:
I think he is extremely busy to get CM 7 and 6.2 fully working and this can take some time so probably this project has to wait some time :)
[Galaxy 3 Android Development] tom3q:
Yes, I'm extremely busy with CM7 and 3.0 kernel for Spica indeed and this project hasn't gotten any new active developers yet.
[Galaxy 3 Android Development] Blackyx007:
As far is i know Marcellusbe is the only one with the required knowledge for this project... (sorry if i forget a dev :D)

If there are Devs who can/want to take a part in this project (maybe you :P) it would be very nice :)