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 19:25:23 +0100
From:	Andreas Werner <wernerandy@....de>
To:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Black screen with GMA500 driver on Atom E680 (invalid VBT
 signature)

On Thu, Nov 14, 2013 at 01:52:09PM +0000, One Thousand Gnomes wrote:
> > My question now is, is it a bug in the driver or in the VGA Bios?
> > 
> > I´ve checked the VGA bios and did a hex dump but there is really no "$VBT" string.
> > On an Atom Gen1 CPU with intel GMA500 Graphic there is the string in the VGA BIOS.
> > But if i create the VGA BIOS for intel Atom E680 which has a GMA600 Graphic
> > there is no string.
> > 
> > Does anybody of you running the GMA500 driver with and Atom E680 without having this
> > problem? Or does anybody know how to get this string into the VGA BIOS?
> 
> E680 I believe will try and use the other style of parsing. I never got
> my hands on one to confirm that but in general E6xx seems to use
> Moorestown style tables instead and you'll only get support for some
> outputs.
> 
Hi,
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" ?

Regards
Andy
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ