<Wizzup>
well, working fbdev in the sense that the X11 fbturbo and fbdev can use it
<dddh>
my chromebook didn't arrive yet
<Wizzup>
hehe
<Wizzup>
okay ;-)
<dddh>
want to be ready :)
<dddh>
I hope chromebook 13.3" will be fast enough
<Wizzup>
we're also looking at mainline support for the previous one (snow), and mainline support for this crb2 (peach), but we're not sure if it is ready yet
<Wizzup>
for example, B.L. needs some work to enable all cores
<Wizzup>
It works on mainline, not on chromeos kernel I think
<dddh>
I guess it is similar to odroid
<Wizzup>
well, this one can enable big and little at the same time
<Wizzup>
as in, the hw can do it, I think that was not the case with one of the odroid octacores
<Wizzup>
ssvb: I have little knowledge of X, xrandr and kms/modesetting - but would it be hard to take randr code from xf86-video-modesetting and/or xf86-video-armsoc and have that in fbturbo? or equivalently, take the accel code from fbturbo and apply that to a modesetting codebase?
<Wizzup>
(with the end result being a somewhat xrandr capable accelerated (or at least fast) ddx
<Wizzup>
)
<liquidAcid>
Wizzup, wouldn't you use this on an emulated fbdev anyway?
<Wizzup>
liquidAcid: basically I want to use fbturbo on an external display - I don't know if that typically has an fb?
<liquidAcid>
Wizzup, which driver is it?
<Wizzup>
ehm, exynos :)
<Wizzup>
What do you mean?
<liquidAcid>
exynos only provides fbdev emulated from fbdev helper
<liquidAcid>
and afaik fbdev helper doesn't implement any kind of dynamic settings
<liquidAcid>
once you have it, the configuration is fixed
<Wizzup>
right, so how does, say, armsoc enable external displays?
<Wizzup>
maybe I should just dive into docs...
<liquidAcid>
armsoc doesn't use fbdev
<liquidAcid>
it uses drm
<Wizzup>
right
<Wizzup>
(I did know that, but I don't know how I can phrase my questions better, so I won't, for now)
<liquidAcid>
what do you mean by external displays anyway?
<liquidAcid>
hdmi?
<Wizzup>
yes
<liquidAcid>
hdmi is just another drm connector
<Wizzup>
I'm interested in somehow getting fbturbo to work on hdmi, so I guess I would need to set up another 'emulated' fb for that?
<liquidAcid>
yes, but the fbdev helper infrastructure should already do that automatically
<liquidAcid>
for every connector it should create a emulated fbdev