Re: [Linux-fbdev-devel] KMS + fb + FBIOPUT_VSCREENINFO

[Sergey Kvachonok]

> The problem we've had is defining proper semantics for what happens in
> multi-output systems when
> you call this ioctl. Which crtc/output should it set the mode on?
> what happens if the mode isn't valid on all
> connected monitors etc.

Does it really makes all that much sense to run different monitors
with the same mode?
Like embedded notebook panel with weird native resolution and an
external CRT/LCD with
completely unrelated native/preferred modes.

I tried running 2.6.29.1 i915 with one fb per crtc mode,
the first thing it did was to shut down embedded panel and to attach
fbcon to external display.
As fbset doesn't work I couldn't bring the panel back to life, and the
whole thing hung when I con2fb'd one of the VTs to it. Can't provide
more specific data atm, didn't yet try to reproduce   the crash.

BTW fbxine and I believe directfb too use FBIOPUT_VSCREENINFO to
adjust vyres to the maximum to allocate offscreen surfaces for page
flipping.
It isn't really modesetting, but rather framebuffer operation, so is
the color depth setting.
At least these can be painlessly provided with the current setup.

Thanks for listening to my rant,
Sergey
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/