| 04:44.32 | *** join/#openezx CoreDuo (coreduo@2001:470:b163::15) |
| 07:58.17 | *** join/#openezx bluelightning (~paul@cpc9-lewi14-2-0-cust183.2-4.cable.virginmedia.com) |
| 07:58.17 | *** join/#openezx bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 08:05.50 | *** join/#openezx flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 08:21.42 | *** join/#openezx ao2 (~ao2@2001:1418:117::1) |
| 08:31.13 | *** join/#openezx mickey|office (~Mickey@business-092-079-168-007.static.arcor-ip.net) |
| 09:50.48 | *** join/#openezx bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 09:57.06 | *** join/#openezx bluelightning_ (~paul@cpc9-lewi14-2-0-cust183.2-4.cable.virginmedia.com) |
| 09:57.06 | *** join/#openezx bluelightning_ (~paul@pdpc/supporter/professional/bluelightning) |
| 10:34.06 | *** join/#openezx flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 12:44.38 | *** join/#openezx mickey|office (~Mickey@business-092-079-168-007.static.arcor-ip.net) |
| 13:17.34 | *** join/#openezx florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 13:35.25 | mickey|office | is there any kind of hardware accelleration on EZX? |
| 13:35.31 | mickey|office | (for gfx, that is) |
| 13:35.53 | mickey|office | or nothing beyond pxafb? |
| 13:37.05 | mickey|office | and... can any remind me about the pxafb capabilities? we have more than just a plain layer, didn't we? |
| 13:37.18 | mickey|office | it's been so long... |
| 14:31.00 | ao2 | mickey|office, pxafb it is, there is some overlay support for transparency and hardware cursor IIRC let me search something about it |
| 14:32.36 | ao2 | someone even talked about allocating the memory for the fb in SRAM rather than DRAM in order to speed up things, but I don't know if that is actually feasible |
| 14:35.14 | ao2 | http://www.kernel.org/doc/Documentation/fb/pxafb.txt last section, but I don't know if that is useful to you |
| 14:39.04 | ao2 | mickey|office, in this article they also talk about a Xscale kdrive driver which is capable of transparency: http://www.linuxsymposium.org/archives/OLS/Reprints-2008/murphy-reprint.pdf but there is no code available that I know of |
| 14:40.21 | mickey|office | ok, thanks, so theoretically the 3 framebuffers are composed w/ alphachannel, but IIRC there were depth limitations in fb1 and fb2. i'll play a bit around, |
| 14:43.22 | ao2 | I recall of some configuration of 19bpp when you can use 1 bit for transparency, but honestly I don't recall if this limitation of the depth is imposed by the screen maybe you can tell me more about that |
| 14:48.47 | ao2 | here is a summary about different overlay capabilities: http://www.shugendo.org/downloads/eye_candy.pdf |
| 14:50.43 | ao2 | it looks like only overlay 1 supports transparency |
| 14:51.25 | mickey|office | right |
| 14:51.35 | mickey|office | hmm, i wonder whether it's worth to try adding support for that |
| 14:51.52 | mickey|office | as it's more universal and probably only slightly slower when done by the software compositor |
| 14:57.09 | mickey|office | afaik the MOTO software is only using this for the camera app |
| 14:59.16 | ao2 | I'd say try to mail the ALP people from that presentation to see if there is code you can reuse, if not just give up :) |
| 15:01.34 | mickey|office | sounds good. lefty is no longer with access, but i'll ask him anyways |
| 16:24.28 | *** join/#openezx purl (~purl@rikers.org) |
| 16:24.28 | *** topic/#openezx is OpenEZX Developer Lounge -- http://www.openezx.org -- identi.ca: http://identi.ca/openezx -- Facebook group: http://www.facebook.com/group.php?gid=291471230258 |
| 16:35.40 | *** join/#openezx mickey|office (~Mickey@business-092-079-168-007.static.arcor-ip.net) |
| 16:36.05 | *** join/#openezx angelox_123 (~angelo@201-92-240-70.dsl.telesp.net.br) |
| 17:02.51 | *** join/#openezx stefan_schmidt (~stefan@p4FC764BA.dip.t-dialin.net) |
| 17:58.27 | *** join/#openezx lclaudio (~lclaudio@177.16.135.103) |
| 19:04.11 | *** join/#openezx parmaste1 (par@dipole.idlepattern.com) |
| 19:33.20 | *** join/#openezx Varunb (~rey@122.162.53.144) |
| 19:45.32 | *** part/#openezx Varunb (~rey@122.162.53.144) |
| 19:54.57 | *** join/#openezx florian (~fuchs@sign-4d0946d5.pool.mediaWays.net) |
| 19:54.57 | *** join/#openezx florian (~fuchs@Maemo/community/contributor/florian) |
| 20:37.09 | *** join/#openezx pixel____ (~root@p5B0E0AA7.dip0.t-ipconnect.de) |
| 20:49.39 | angelox_123 | ao2,i was seeing on OpenEmbedded tree on motorola-ezx-base.inc that haves the line "PREFERRED_PROVIDER_virtual/xserver = "xserver-kdrive"",wouldn't be more good use xorg-xserver? it can run on a1200,e6 finely (with correct colours and without seg faults)... |
| 21:23.17 | WyrM | ao2: the #ifdef CONFIG_REGULATOR on mmc_spi is really needed. Unless the regulator api was changed to return error on regulator_get if config_regulator is not defined. |
| 21:24.45 | ao2 | angelox_123, I'll try that |
| 21:25.42 | ao2 | WyrM, regulator_get() now is a tub returning NULL when CONFIG_REGULATOR is not defined, I don't know if that is a recent addition |
| 21:25.50 | ao2 | s/tub/stub/ |
| 21:26.37 | WyrM | ao2: good, makes more sense now. At the time i wrote the pxamci regulator support is was returning a "dummy regulator". |
| 21:26.57 | WyrM | i guess the ifdefs may be removed from pxamci too then... |
| 21:27.17 | ao2 | you stole my words :) |
| 21:32.38 | angelox_123 | ao2,i was thinking in do what you said to me some time ago.. |
| 21:32.53 | angelox_123 | remove metano.conf from distro and make it a image file only |
| 21:33.00 | angelox_123 | i think it'll be good for both sides :) |
| 21:37.23 | ao2 | good |
| 21:41.39 | angelox_123 | if you want/can you can remove it anytime ok? :D i made my decision |
| 21:43.24 | ao2 | angelox_123, if you want to propose the virtual/xserver change yourself too feel free to do so, but please do some comparative tests like: how much memory does kdrive Xfbdev take and how much memory does xorg-xserved with fbdev driver take? I mean ram allocated when loaded. |
| 21:44.28 | ao2 | about the metano changes, take your time, test the image, remove the distro and send patches to openembedded-devel I can apply them after some quick review |
| 21:45.29 | angelox_123 | ok thanks,i'll try make these tests |
| 21:45.52 | angelox_123 | and thanks again by Metano subject.... |