Hello,
On Fri, 12 Apr 2013 18:28:26 -0500
Nishanth Menon wrote:
> From: Paul Sokolovsky
>
> An ifdef in drm.h expects to be compiled with full-fledged Linux
> toolchain, but it's common to compile kernel with just bare-metal
> toolchain which doesn't define __linux__. So, also
Hello,
On Fri, 12 Apr 2013 18:28:26 -0500
Nishanth Menon n...@ti.com wrote:
From: Paul Sokolovsky paul.sokolov...@linaro.org
An ifdef in drm.h expects to be compiled with full-fledged Linux
toolchain, but it's common to compile kernel with just bare-metal
toolchain which doesn't define
Hello,
On Tue, 23 Nov 2010 02:00:51 -0500
Alex Deucher wrote:
[]
> > My specific issue is that there's an LVDS (of MSI X410/X430
> > notebook) which has right dimensions and refresh rate, but wrong,
> > if not say unrelated, clock settings. The end result is that
> > there's tearing-off,
Hello,
There're cases when EDID may be present, but be just severely (or
seemingly) broken. Is it possible to completely and unconditionally
ignore any EDID info for KMS, and instead use user-supplied parameters?
I googled the following message:
http://www.mail-archive.com/dri-devel at
Hello,
On Tue, 23 Nov 2010 02:00:51 -0500
Alex Deucher alexdeuc...@gmail.com wrote:
[]
My specific issue is that there's an LVDS (of MSI X410/X430
notebook) which has right dimensions and refresh rate, but wrong,
if not say unrelated, clock settings. The end result is that
there's
Hello,
There're cases when EDID may be present, but be just severely (or
seemingly) broken. Is it possible to completely and unconditionally
ignore any EDID info for KMS, and instead use user-supplied parameters?
I googled the following message:
