From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Andreas Werner <wernerandy@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Black screen with GMA500 driver on Atom E680 (invalid VBT signature)
Date: Mon, 18 Nov 2013 13:59:26 +0000 [thread overview]
Message-ID: <20131118135926.650e9904@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20131116092838.GA2564@thinkpad.fritz.box>
> if i dump the memory on 0xFC of the config space, there is just some from the
> BIOS vendor with a BIOS Version, but nothing like $GCT.
Ok
> In the Datasheet the 0xFC is described as "storage" does it mean there should
> be the settings for the Graphic like VBT?
> I did not find more information abaout GCT and how to implement it.
Its one place it can be. I don't believe there is any public
documentation.
> The board uses sdvo->vga for the output, the second board
> uses sdvo->DVI and LVDS but there is always a black screen on each
> output interface. So i think there is wether a VBT not a GCT.
Fair enough. The current state is basically that some E600T devices happen
to work on certain ports (the logic is similar enough). If you've got one
that doesn't then you are basically on your own.
The last "official" Intel out of tree driver is EMGD 1.18 which supports
Fedora 14 and a couple of other obsolete distros. It may be possible to
use the open bits of that as a basis of adding E680T support but it's
probably a couple of months work for someone sufficiently insa^Wmotivated.
Alan
prev parent reply other threads:[~2013-11-18 13:59 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
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 [this message]
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=20131118135926.650e9904@alan.etchedpixels.co.uk \
--to=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).