linux-kernel - Re: gma500: Cannot find any crtc or sizes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120612121527.6d3ab653@pyramind.ukuu.org.uk>
Date:	Tue, 12 Jun 2012 12:15:27 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Patrik Jakobsson <patrik.r.jakobsson@...il.com>
Cc:	Christian Gmeiner <christian.gmeiner@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: gma500: Cannot find any crtc or sizes - going 1024x768

> You're hitting a bug in the IS_MRST macro. You might actually have the fuse
> value but IS_MRST returns false for 0x4108. Try the following patch:

If its an Oaktrail device then it should be using the PC BIOS data anyway
I would have thought. Only Moorestown should be using the other style of
data and Moorestown never became a real product.

However if the panel is on the SDVO port then the BIOS data would appear
to be correct as it isn't on the LVDS channel but bridged off the SDVO.

In that case it'll need SDVO support sorting out.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/