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]
Date:	Thu, 14 Nov 2013 20:57:58 +0000
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Andreas Werner <wernerandy@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Black screen with GMA500 driver on Atom E680 (invalid VBT
 signature)

> but if you checkout the PCI table in the driver, there is the device
> and vendor ID mentioned, that means for me that the driver supports
> the Graphic core in E680.
> And after loading the driver, it will parse for $VBT.
> I just find a comment in the PCI table with "E620" but
> the device and vendor id is the same for E680.
> 
> What do you mean with "Moorestown style" ?

There are essentially two styles of configuration table used with PVR
graphics. One is basically the same as that used on 'real' Intel graphics
the other first introduced with one of the SoC devices is a firmware
table in a completely different format.

The netbook and PC oriented devices use the VBT, the tablet SoC
devices and embedded ones seem to vary and have a VBT/GCT in different
form that is found via config 0xFC on the chipset - see mid_bios.c

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/

Powered by blists - more mailing lists