Le 08/05/2012 14:41, Alexander Graf a écrit :
On 08.05.2012, at 14:33, Guillaume Gardet wrote:
Hi,
During the last ARM config update I enabled framebuffer for all devices. I also enabled some DRM drivers (for omap for example) to be able to choose between FB and DRM.
What is the best way: Framebuffer or DRM? Maybe it depends on the board used. It may also have a V4L display on some boards.
DRM should autoselect configuration (resolution, etc.) depending on the monitor/TV used. But it seems you cannot lower the resolution to gain in responsiveness. Framebuffer must be configured to have a given config. Without config it uses 640x480 as default (at least for omapfb) which is a very low resolution which cannot be displayed on most TV. Maybe we should configure all our boards to have a higher default resolution such as 800x600 or 1024x768 to be able to use a monitor or a TV.
I think we should have both as modules (to let the final user to have the choice) and add a config file to load one (framebuffer?) as default. I thought usually you have a fb driver (which again should use KSM) to get a usable screen for text mode and once X takes over, it uses DRM through the device specific driver, no?
X can also use Framebuffer (see: xorg-x11-drv-omapfb). I am not sure if both can coexist. I can load both at the same time manually (I did not test if it works). Loading omapdrm does not load omapfb, so it cannot use it directly but it may have his own implementation of the fb. I will try to test it. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org