yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] kylandomos:
I don't think you imagine the work it would be.

Our Dev's should do that if they can . ( If they want )

I think that Tom3q have too many project Atm ( Openfimg // Kernel 3.X // CM7 + CM9 ==> All For Spica and doing it Alone ) so even if he would do that, he won't get much time .

Just do as Always, Impress us Tom3q ;) . Openfimg is ever a Great Deal !
[Galaxy 3 Android Development] moikop:
Awesome. I think ttySAC1 is defined as s3c2410_serial1 in the kernel.

I still don't understand why all I get this � weird character :/

Vcc connected to 3.3v, 150k ohm (though tried with 619k too) resistor and baud rate 115200 8N1, right? :confused:
[Galaxy 3 Android Development] tom3q:
Maybe something wrong with your level converter?

Also, if I decoded color codes of resistors correctly, I have 522k ohms connected between GND and ID pins (two 1M connected in parallel and additional 22k after them).

Edit: Would make sense, as according to http://xdaforums.com/showthread.php?t=820275 it would be

RID_FM_BOOT_OFF_UART,	/* 1 1 1 0 0	523K	Factory Mode Boot OFF-UART */
[Galaxy 3 Android Development] moikop:
Tried with both, 522k & 523k (just in case) and still the same.. So it's gotta be my level converter... that's weird :S
[Galaxy 3 Android Development] tom3q:
Just for reference, my level converter: http://translate.google.com/transla...unikacja-przez-usb---modul-em212.html&act=url

EDIT: Maybe we should create new topic for discussion on such things?
[Galaxy 3 Android Development] Piraze91:
Now on ics we don't need to reduce anything for play to gangstar w.c.h smoothly but there are some white textures withfimg. So my queston is, will we need to reduce something on chainefire for play when the openfimg will be done ?

Envoyé depuis Cyanogenmod 9 build 4
[Galaxy 3 Android Development] tom3q:
You'll see then. The only way to check that is to test some running code. As for chainfire alone, I don't think it will be of any use with OpenFIMG.
[Galaxy 3 Android Development] CroNk3r:
try to change plugins in chainfire nad tell us if it worked :D
[Galaxy 3 Android Development] Arakmar:
I just finished to implement power management in the G3D module.

6 last commits : https://github.com/Arakmar/G3MOD/commits/master

It works just fine without USE_G3D_DOMAIN_GATING. Power up/down is correctly activated in suspend/resume.

But I have some issue while using USE_G3D_DOMAIN_GATING.

The phone boots ok and the idle timer seems to work. But when I switch off the screen, it doesn't want to wake up anymore.

After debugging that, it's because of some calls to the FLUSH ioctl (between a LOCK and UNLOCK) which failed here in g3d_flush_pipeline :

if(!wait_for_completion_interruptible_timeout(&d_completion,
G3D_TIMEOUT))

Do you have any ideas ?
[Galaxy 3 Android Development] tom3q:
I wonder why you moved almost all the data out of the structure into global variables. Structure is the preferred way of storing driver data according to Linux kernel programming guidelines, while global variables are strongly discouraged. Needless to say that you unnecessarily diverged from my code making merging of any future changes automatically almost impossible.

Another thing is that in s3c_g3d_suspend it should be first checked whether the hardware lock is released and then proceed with hardware power off only if it is. This is to prevent a situation that suspend is requested before the userspace releases hardware lock.
[Galaxy 3 Android Development] Arakmar:
When I was investigating why openFIMG didn't work on G3, I found that the data structure wasn't valid anymore after the probe.

For instance, if I use the data structure in mmap to get the start address, I have a kernel panic due to a segfault. (same problem in ioctl)

So, after moving all the content of the structure into global var, it worked.

Done.

https://github.com/Arakmar/G3MOD/commit/9f044ef8ec8c82fe94d4d64b056919fb36814d50

But I just notice that suspend isn't called anymore after removing dev_pm_ops and the use of suspend/resume directly in the platform_driver struct.

I did that in this commit : https://github.com/Arakmar/G3MOD/commit/f842435d3b2e43a9b3213ee48ffb1a6415a937bf

Do I need to keep that ?
[Galaxy 3 Android Development] tom3q:
I don't like this way of solving problems. In addition, I can assure you that structure wasn't the problem.

Both methods are legal and should work fine, although dev_pm_ops is the new and preferred one to specify power management callbacks. Of course only one method can be used at a time.
[Galaxy 3 Android Development] Arakmar:
I haven't kernel panic output, so it's pretty hard to find where is the problem.

The only thing I'm sure is that when I want to access an element of the data structure => Kernel panic.

But I'll receive my uart adapter soon, so I'll have more infos about that.

Thanks for the explanations. I'll go back to dev_pm_ops as it worked just fine.
[Galaxy 3 Android Development] tom3q:
Another update pushed to the repository. It adds shader cache, which should reduce CPU usage in case when GL state is often changed by the application and so improve performance in such cases. (It's the remaining part of the optimization I talked about some time ago.)
[Galaxy 3 Android Development] Uberzone:
Can someone compile this new updated libs ?)
[Galaxy 3 Android Development] sambatboy:
in this post harkan has compile it. http://xdaforums.com/showpost.php?p=23543189&postcount=1576
[Galaxy 3 Android Development] Arakmar:
New version of my kernel (with G3D power management) :

http://dl.dropbox.com/u/12943198/ics26_arakmar_signed.zip

Latest build of openfimg + my new version of the kernel :

http://dl.dropbox.com/u/12943198/openFIMG_Arakmar_signed.zip
[Galaxy 3 Android Development] pkatsaras:
Can this be used with froyo rom as well?
[Galaxy 3 Android Development] Arakmar:
No, only ICS, MIUI, CM7.
[Galaxy 3 Android Development] Pinak.ahuja:
The same fimg libs can be used for ics as well as gb?
[Galaxy 3 Android Development] raveathon:
Great I will try with the new Update :)
[Galaxy 3 Android Development] makalele2:
Is this stable? Are the games really going faster :) ?
[Galaxy 3 Android Development] TheCreat:
As will I, flashing now...

Swyped on my Galaxy 3
[Galaxy 3 Android Development] KSLevel11:
Anyone tried the newest update on Froyo ROM? If yes, how is performance? (Not in games, but in normal use).

Can we expect NON-OC versions of this kernels?
[Galaxy 3 Android Development] Shree_Jamdar:
Hi

Sorry I don't keep myself updated regularly, but i am on CM7 so I know i can flash this. But which one? . what if i want both? ie power management & open FIMG? and is you kernel ok with backup/restore on cm7, bluetooth & wifi? It would be really nice if you start a new thread with all your kernels and features, changlog etc. Just a suggestion :)
[Galaxy 3 Android Development] KSLevel11:
I think, that second kernel (OpenFimg + kernel) contains G3D Power Managment :)
[Galaxy 3 Android Development] pkatsaras:
Tried on froyo but I got stuck on first screen...Tried to reflash another kernel but still the same...Any ideas???
[Galaxy 3 Android Development] KSLevel11:
Did you try wipe cache&dalvik after update?
[Galaxy 3 Android Development] pkatsaras:
Dalvik cache only...I'll try again both...

Edit: Still no good...

Edit2: Can't mount e:\
[Galaxy 3 Android Development] Uberzone:
An amazing Job - almost no flickering UI on CM7

Thanks Tom3q & Arakmar
[Galaxy 3 Android Development] tom3q:
Have you finally managed to get rid of the hangs? What was the problem?
[Galaxy 3 Android Development] TheCreat:
I've only used it for about an hour so far, but at least so far everything went perfect. It even feels smoother occasionally (but that might be a placebo effect).

Again, thank you VERY MUCH (!) for the compiled fimg libs and the updated kernel!

(and for the development going into both in the first place, of course)
[Galaxy 3 Android Development] Jason-EX:
Hi all, I have a query....will FIMG driver work in froyo properly? (sry, i'm a noob in this kind of stuff)

Thanks in advance!
[Galaxy 3 Android Development] rubensollie:
Do you maybe know why i always have to change the gralloc.GT-I5800 to gralloc.s5p6442, cause i get a purple line on top with some green lines.
[Galaxy 3 Android Development] Arakmar:
Yes, it works with domain gating now :)

It was the issue you pointed out in your message about the check if the hardware is still locked.

---------- Post added at 04:07 PM ---------- Previous post was at 04:04 PM ----------

I just tested on Froyo and it doesn't boot because of the gralloc (link error).

Samsung's one seems to have some hack inside to make it work with their surfaceflinger ...
[Galaxy 3 Android Development] KSLevel11:
Will you try to fix this? It would be great if we would have OpenFimg @ Froyo.
[Galaxy 3 Android Development] Jason-EX:
so how do i solve that problem.....?

EDIT: yeh, i got stuck in the sumsung bootscreen too....

and btw, Chirayu desai (cdesai) told me the way to fix it for froyo....so i will give it a try tomorrow :)
[Galaxy 3 Android Development] propsia:
awesome work

@tom3q @akarmar

nice job now screen transitions are so smooth and on MIUI the akarmars kernel is now rocking

thanks tom you are really genius and thanks to you too akarmar

:-)
[Galaxy 3 Android Development] Michael1101:
For me, on CM9 a4, the purple lines also occure. The renaming didn't work for me. Had to flash a different kernel again :(
[Galaxy 3 Android Development] rubensollie:
You have to delete the gralloc.GT-I5800 from /system/lib/hw And install the update.zip on one of my latest post on my miui thread, then it should work :p
[Galaxy 3 Android Development] tom3q:
Another bunch of updates in my repository, but nothing particularly interesting to make it worth upgrading.
[Galaxy 3 Android Development] andreapier:
You are working hard these days don't you? Well, i'm very pleased about it!

Keep on the great job!
[Galaxy 3 Android Development] tom3q:
Hehe :). At the moment I'm more just adding whatever comes to my mind from time to time (as this is also my hobby) when I don't have any other duties (as I'm a somewhat busy person). When I find more free time to implement lighting, this will be some real hard work ;).
[Galaxy 3 Android Development] andreapier:
Oh, i know you are busy (who is not actually?;))

But if this are the results of your business, hey man, i hope you are always busy!

Just joking of course. What is important is that you keep on working to this project even if slowly. We are waiting for more than a year for complete CM7, so we can wait for your work too.

Don't worry!
[Galaxy 3 Android Development] tom3q:
Could you put last version of your module in your repository? It seems like people working on OpenFIMG for Samsung Transform and Moment are having exactly the same problem, also with 2.6.32 kernel from Samsung, so they could use your version as reference.
[Galaxy 3 Android Development] Hordon:
HI! Is there any chance to make work with this gpu drivers the tsf launcher... I just asking that because in kyrillos rom v9 this launcher show error but when i switched to cm9 for g3 rom (include your fimg) make the launcher work but bed resolution.. Thanks!
[Galaxy 3 Android Development] fehery:
Szia,mia helyzet a TSF-fel? Tudsz valamit tanácsolni?
[Galaxy 3 Android Development] sharukins:
english please...
[Galaxy 3 Android Development] Jason-EX:
this driver won't work in froyo...
[Galaxy 3 Android Development] fehery:
Hi, TSF, what about you, can you help?
[Galaxy 3 Android Development] Hordon:
Ok, but CM9 for g3 is ICS, not froyo. I just noticed the driver make work tsf (partly), what doesn't work in froyo. My question is: is there any chance to make fully work tsf?

Thanks!

---------- Post added at 09:13 AM ---------- Previous post was at 09:12 AM ----------

Not work yet..
[Galaxy 3 Android Development] sharukins:
probably yes, but there are still several features missing. it's possible that when openFIMG is completely done the tsf will work without any need of further bugfixing. but you need to wait to see if that's the case.
[Galaxy 3 Android Development] austin266:
Is there any difference btw 3.0 kernel and ours 2.6.32 kernel

@tom3q thanx alot for ur work mate

R u going to build 3.0 kernel for sg3

cm7 by marcellusbe

800mhz kernel
[Galaxy 3 Android Development] tom3q:
It's not the version which matters (although sometimes it does too), but the code inside. My 3.0.x kernel for Spica is based entirely on clean Android kernel sources, without any original code from Samsung and with all the missing drivers rewritten by me.

You're welcome.

Yes, I'm going to work on it with other G3 developers, when I find some time. It shouldn't be bound to any particular version of Linux kernel. It will be a clean kernel based on latest mainline sources available at the time.
[Galaxy 3 Android Development] Jason-EX:
I want to work with you guys too :D:D:p:p
[Galaxy 3 Android Development] sarthak.killedar:
Thanke for the news! Great work with OpenFIMG! All graphical processing will be done by GPU rather than CPU with OpenFIMG, right?
[Galaxy 3 Android Development] sharukins:
depends on the version of android. on ICS all graphical processing is done by GPU while on older versions graphics surface of android is rendered by the CPU
[Galaxy 3 Android Development] sarthak.killedar:
GPU rendering is always good then software rendering, right? Clearing my basics of understanding!
[Galaxy 3 Android Development] KSLevel11:
If I want to flash second of this kernels:

Need I flash previous updates with OpenFimg?
[Galaxy 3 Android Development] harkan89:
It reduces the load on the cpu for starters :p
[Galaxy 3 Android Development] alen1901:
No, just flash that.

Sent from my Nexus S
[Galaxy 3 Android Development] tom3q:
Yes, but it needs a GPU and proper drivers for it. First Android phones (and also some newer) didn't have a GPU at all and drivers for those which had were buggy. At least this is Google's argumentation for their design decision about software rendering.
[Galaxy 3 Android Development] Arakmar:
My latest module is here : https://github.com/Arakmar/G3MOD/tree/master/Kernel/drivers/media/s5p6442/g3d_drv_openfimg

But, finally I was wrong, with domain gating enabled, I notice that it doesn't work all the time.

Sometimes it works, sometime the screen doesn't wake up ...

I'll investigate that a bit more when I'll get some free time.

But without the domain gating it works just fine. It's disabled in the kernel I released some days ago.

Could you give the links of the forum threads about Transform and Moment ?
[Galaxy 3 Android Development] tom3q:
I recall having problems with domain gating on 2.6.32 kernel for Spica too. I don't remember if it was fixed, so it's possible that it wasn't. So it's possible that the domain gating API is somewhat broken and some of the assumption I took when implementing PM in g3d module for it is in fact false.

CM7 for Transform: http://forum.sdx-developers.com/?topic=18747.0
[Galaxy 3 Android Development] eeshlikhith:
Linux Kernel 3.3 is out with some Android code merged in. Could it be of any help?
[Galaxy 3 Android Development] tom3q:
This is the code that's already in Google's Android kernels and is needed to run Android. Moreover, it's just the essential part that got merged. Power management extensions (wakelocks and co.) are still missing.

Anyway, this isn't anything that affects us. For mobile devices the best starting point is Android kernel tree, which is the same as mainline, but contains all the extensions from Google.
[Galaxy 3 Android Development] Halco:
Tom3q, and others dev's, what ur advice for a stock Froyo ROM ? Should i have to let the stock kernel ? Or flash another that support Open FIMG ?

(For a good battery life and performance i mean)
[Galaxy 3 Android Development] tom3q:
AFAIK OpenFIMG doesn't work with Froyo G3 ROMs, because of Samsung's patched libraries.
[Galaxy 3 Android Development] KSLevel11:
So, we never get OpenFIMG dribers at froyo? Or is there a chance?
[Galaxy 3 Android Development] tom3q:
One of the devs would have to make a clean Froyo ROM without Samsung's libs. IMHO waste of time that could be otherwise spent on working on CM7, ICS and/or new kernel.
[Galaxy 3 Android Development] Halco:
Ok. I prefer that they spend their free time in cm7/9 too ^^

Envoyé depuis mon GT-I5801 avec Tapatalk
[Galaxy 3 Android Development] Jason-EX:
yeh, working on clean froyo will be a waste of time......
[Galaxy 3 Android Development] bscraze:
With tom its definitely possible just a matter of whether its priority and if he has the time to do so :p

Cheers:)

Sent from my GT-i9003 powered by Titanium rom S
[Galaxy 3 Android Development] sharukins:
how about reading previous posts before posting...?

tom said that one of the devs would have to make a ROM without the samsung libraries, which is a waste of time.

especially considering that there are much more important things to do with GB and ICS
[Galaxy 3 Android Development] m1trand1r:
^^^^^very well said...;)^^^^

~~~~~~~~~~~~~~~~~~~~~~~~~

Sent from Galaxy

Hercolubus' Rom v 1.0

powered by

Team G3mod-ICS26 kernel by Arakmar

~~~~~~~~~~~~~~~~~~~~~~~~~
[Galaxy 3 Android Development] CroNk3r:
This project(http://xdaforums.com/showthread.php?p=23888289#post23888289)will make tom's life easier :D
[Galaxy 3 Android Development] josip-k:
Only if dharam is gonna make 3.0 kernel,no one knows whats he gonna do ;)
[Galaxy 3 Android Development] sharukins:
well, kernel developement won't help writing the GPU driver and as long as dharam isn't porting a later kernel version than the one we are using now this won't impact openFIMG developement at all.
[Galaxy 3 Android Development] tom3q:
Please put sources of this exact version somewhere and I'll look for errors.
[Galaxy 3 Android Development] Arakmar:
Ok thanks.

Here are the sources : https://github.com/Arakmar/G3MOD

Branch : crashOpenfimg
[Galaxy 3 Android Development] tom3q:
Should be fixed with this commit applied (added in newer kernels):

https://github.com/tom3q/spica-3.0/commit/fa1f68db6ca7ebb6fc4487ac215bffba06c01c28
[Galaxy 3 Android Development] bscraze:
The reason I mentioned priority :p. You guys didn't really catch my point there, perhaps it was too subtle. Anyway you said it so no need for me to explain myself ;)

Cheers:)

Sent from my GT-i9003 powered by Titanium rom S
[Galaxy 3 Android Development] sarthak.killedar:
What Angry Birds Space required? Both format of drivers giving the White Textures! Can you look at that when you get some time?
[Galaxy 3 Android Development] josip-k:
+1 for that!and also for angry birds rio
[Galaxy 3 Android Development] tom3q:
Probably too much video memory.
[Galaxy 3 Android Development] sarthak.killedar:
So it probably means we can not play that game on Samsung Galaxy 3..........
[Galaxy 3 Android Development] josip-k:
I think it would be pointless to install cf3d just for angry birds..
[Galaxy 3 Android Development] Jason-EX:
Angry birds Rio is working PERFECTLY! but I haven't try angry birds space yet :p
[Galaxy 3 Android Development] kyrillos13:
Yeah rio works fine. But Angry Birds Seasons & Angry Birds Space dont;p
[Galaxy 3 Android Development] tom3q:
Yes, if the theory with video memory is true, at least until static reserved memory mapping of current kernels gets replaced with something smart, like Direct Rendering Manager or I add some smart memory management trick to OpenFIMG to overcome the limitations of static reserved memory, whichever comes first.
[Galaxy 3 Android Development] josip-k:
So will you do something like that in the future?
[Galaxy 3 Android Development] alb3rtt:
the latest rio? i downloaded the latest from the market and i get white background (using openfimg). i downloaded the one from the russian website and it works perfectly just it only has the first section :p Angry birds works perfectly with openfimg. (The one from the russian website).
[Galaxy 3 Android Development] tom3q:
Yes, moving to Direct Rendering Manager is in the long term schedule. As for memory management trick, I didn't think of anything interesting yet.
[Galaxy 3 Android Development] josip-k:
Great :D so wich bugs are left?
[Galaxy 3 Android Development] tom3q:
All the problems which can be seen in Gallery 3D and in corridor test in Quadrant with volumetric shadows enabled. And all the unknown ones of course. + all the features unimplemented yet (but can't be called bugs)
[Galaxy 3 Android Development] Jason-EX:
the older versions of angry birds seasons works perfectly with CF3D driver and qualcomm plugin though.....:p
[Galaxy 3 Android Development] Spitlebug:
RAM drive using the onboard memory on the phone? Might mean laggy performance, but at least it will work...
[Galaxy 3 Android Development] tom3q:
I'm not sure I understand you.

Video memory is just a reserved (in software) part of the normal onboard RAM.
[Galaxy 3 Android Development] sarthak.killedar:
So what are the unimplemented features yet in OpenFIMG? And you worked on lighting? I'm pretty sure, you are moving fast these days.......
[Galaxy 3 Android Development] D@rekills4:
https://www.github.com/tom3q/openfimg/wiki/Status
[Galaxy 3 Android Development] josip-k:
So wich are the most important things to be implemented?openGL ES features?
[Galaxy 3 Android Development] Spitlebug:
In the DOS days it used to be common to have a TSR (Terminate and Stay Resident) used to access CD-ROMs and load drivers for the CD-ROM. A TSR was simply a place holder in the RAM that acted like a "virtual drive" in which memory registers could be reserved. The advantage to this system was that the TSRs could be loaded into Upper or Extended areas of memory that weren't required by the system. The TSR also had a basic array similar to a FAT in which it kept track of the registers that were availible to it.

I assume that this is also how the Video Memory works, but is it a fixed size or is this something that can be expanded or changed on the fly as required by the GPU?

For example, if it is a fixed size is it possible to load a "proxy" program that reserves additional RAM that the GPU drivers can take advantage of?
[Galaxy 3 Android Development] tom3q:
It's much simpler currently (braindead actually).

G3 has two DRAM chips, one standard 256 MB DDR and another 128 MB OneDRAM. The first chip is fully used for Linux without any restrictions, but OneDRAM is a special chip with the memory divided into 3 blocks: 80 MB dedicated for Application Processor (main CPU), 32 MB dedicated for Baseband Processor (modem) and 16 MB of shared memory (+ some additional logic) for communication between CPU and modem.

Now this 80 MB of OneDRAM isn't directly accessible for Linux (because it's configured in such way) and it's used as reserved memory for hardware buffers. You can see the exact (static) allocation of all the areas here: https://github.com/Arakmar/G3MOD/bl.../arm/plat-s5p64xx/include/plat/reserved_mem.h . Then just all the drivers use their own reserved area, which they can manage themselves. For example pmem_gpu1 (used by OpenFIMG) uses the 40 MB area for G3D.

This isn't the most fortunate solution (and not first one by Samsung), but for now it works.
[Galaxy 3 Android Development] kylandomos:
And is this possible to change all the memory managment to get more Ram and less video reserved ram' ?

As an extension of our memory ?
[Galaxy 3 Android Development] tom3q:
It isn't possible to get outside of the 80 MB area and it's fully used currently (including 40 MB for GPU). Of course most of it is wasted almost all the time, because of this way of allocation. A single dynamic allocator for allocating memory from this area would need to be added and all the drivers using reserved memory modified to use it.
[Galaxy 3 Android Development] josip-k:
So as far i understanded allocating that reserved 80 mb would improove video memory?
[Galaxy 3 Android Development] tom3q:
No. It's already fully used. Without changing the allocation system dramatically nothing can be improved.
[Galaxy 3 Android Development] josip-k:
Can allocating be done?
[Galaxy 3 Android Development] tom3q:
What "allocating" are you talking about?
[Galaxy 3 Android Development] josip-k:
Whole system