09:58 <Wizzup> ssvb: (going to try it soon); any clue if g2d accel on the chromebooks will work with the fbturbo driver? (since it specifically mentions "allwinner a10/a20 g2d" or "sunxi g2d" on the pages I can find)

10:00 <ssvb> Wizzup: no, it will not work without adding special support for it

10:02 <ssvb> Wizzup: regarding your question from the other day, I think that it should be possible to add a new drm/kms backend to fbturbo in addition to the fbdev backend

10:06 <ssvb> Wizzup: it's a different kernel api and it can be abstracted

10:09 <Wizzup> wrt g2d: ack, makes sense, then I won't enable it at this point ;-)

10:10 <Wizzup> wrt drm/kms: ack, would that be a lot of work? I don't know that much about it, I guess :) noteworthy that so far I didn't even get xf86-video-modesetting to work, but I hope the situation improves when I try mainline on peach

10:11 <ssvb> yes, the exynos kernel support for anything graphics related used to be in a pretty bad shape at least a year ago

10:11 <Wizzup> I'm inclined to blame the chromeos tree specifically

10:12 <ssvb> fbdev is still the most reliable way to get a working linux desktop across a wide range of arm hardware

10:12 <Wizzup> but we'll see -- apparently snow and mainline should work ok now

10:13 <ssvb> yes, I personally don't care much about what kernel api to use, but it needs to be stable and functional

10:15 <ssvb> with all the hard work being invested in drm/kms, it should eventually become more usable

10:16 <Wizzup> yeah

13:26 <WarheadsSE> Wizzup: I am using it with armsoc, but I don't think initially it will work with fbturbo for the time being

13:29 <Wizzup> g2d with armsoc?

13:35 <WarheadsSE> mm, point

13:35 <WarheadsSE> it is early and it was a long day/night ... I misread some.