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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 21 Jun 2012 10:55:44 +0200
From:	Christian Gmeiner <christian.gmeiner@...il.com>
To:	Patrik Jakobsson <patrik.r.jakobsson@...il.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <greg@...ah.com>
Subject: Re: gma500: Cannot find any crtc or sizes - going 1024x768

2012/6/13 Patrik Jakobsson <patrik.r.jakobsson@...il.com>:
> On Wed, Jun 13, 2012 at 2:26 PM, Christian Gmeiner
> <christian.gmeiner@...il.com> wrote:
>> 2012/6/13 Alan Cox <alan@...rguk.ukuu.org.uk>:
>>> The basic question is:
>>>
>>> Does this device use the Intel BIOS way of reporting mode information,
>>> or the embedded "GCT" style.
>>>
>>
>> As far as I can tell from the logs, it seems to use the Intel BIOS way.
>>
>> [    2.366174] [drm:psb_intel_opregion_setup], Public ACPI methods supported
>> [    2.366183] [drm:psb_intel_opregion_setup], ASLE supported
>> [    2.366200] gma500 0000:00:02.0: Enabling MSI failed!
>> [    2.366287] [drm] internal display is LVDS display
> Do you still force lvds on as with your first modification or are the fuse
> values being read? As Alan said, we might need to add a DMI quirk
> for this particular board in order to pick LVDS instead of MIPI.
>
> What do you get when running:
> dmidecode -t 1
>

I see a lot "Need to filled by OEM" strings - an other thing to fix in the BIOS.
This should be doable also with the congatec utility.


>> [    2.366363] gma500 0000:00:02.0: SKU values is 0x2a00000.
>> [    2.366371] gma500 0000:00:02.0: LNC core clk is 200MHz.
>> [    2.366389] gma500 0000:00:02.0: drm platform config address is 3ddbd010
>> [    2.366403] ioremap error for 0x3ddbd000-0x3ddbe000, requested 0x10, got 0x0
>> [    2.366484] gma500 0000:00:02.0: Unable to read GCT!
>> [    2.366563] gma500 0000:00:02.0: platform_rev_id is 5
>> [    2.368471] gma500 0000:00:02.0: VBT signature missing
>>
>>
>> I will ask my contact at congatec what they are really using. I hope
>> to get some feedback soon.
>
> As you said in your first post, modes are read from an at24 i2c eeprom,
> so we need to add support for that unless you can live with supplying
> your own modes as boot parameter or in your xorg.conf.
>

Thanks... I will try to generate a VBIOS and see what happens.

--
Christian Gmeiner, MSc
--
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/