From: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Andreas Werner <wernerandy@gmx.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Black screen with GMA500 driver on Atom E680 (invalid VBT signature)
Date: Thu, 14 Nov 2013 16:32:41 +0100	[thread overview]
Message-ID: <CAMeQTsYuP-zMMJS3kLveDf=TWa7SnWVLkS=TFXjP8A-vZ8-nXQ@mail.gmail.com> (raw)
In-Reply-To: <20131114135209.0a8a15ff@alan.etchedpixels.co.uk>
On Thu, Nov 14, 2013 at 2:52 PM, One Thousand Gnomes
<gnomes@lxorguk.ukuu.org.uk> 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.
As Alan says, Moorestown should use GCT as in mid_bios.c and the signature
should be $GCT instead of $VBT. Though I don't know if you get any LVDS info
from from that or just MIPI stuff.
In my last set of patches I included 0x4108 in the IS_MRST macro which might
make gma500 find the LVDS modes via I2C. In the same patchset there is also
support for SDVO on Moorestown.
Patches are available in Dave Airlies drm-next and heading for 3.13-rc1
Thanks
Patrik
next prev parent reply	other threads:[~2013-11-14 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 18:34 Black screen with GMA500 driver on Atom E680 (invalid VBT signature) Andreas Werner
2013-11-14 13:52 ` One Thousand Gnomes
2013-11-14 15:32   ` Patrik Jakobsson [this message]
2013-11-14 18:25   ` Andreas Werner
2013-11-14 20:57     ` One Thousand Gnomes
2013-11-16  9:28       ` Andreas Werner
2013-11-18 13:59         ` One Thousand Gnomes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox
  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):
  git send-email \
    --in-reply-to='CAMeQTsYuP-zMMJS3kLveDf=TWa7SnWVLkS=TFXjP8A-vZ8-nXQ@mail.gmail.com' \
    --to=patrik.r.jakobsson@gmail.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wernerandy@gmx.de \
    /path/to/YOUR_REPLY
  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
  Be sure your reply has a Subject: header at the top and a blank line
  before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).