From: Adam Jackson <ajax@redhat.com>
To: 4ernov <4ernov@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Dear Intel: please document SDVO LVDS option block
Date: Wed, 26 Oct 2011 10:53:11 -0400 [thread overview]
Message-ID: <1319640791.18349.10.camel@atropine> (raw)
In-Reply-To: <1319034493.12938.8.camel@atropine>
[-- Attachment #1.1: Type: text/plain, Size: 714 bytes --]
On Wed, 2011-10-19 at 10:28 -0400, Adam Jackson wrote:
> I assume the SDVO LVDS options block in the VBT would tell us what bits
> are correct to program here, but intel_bios.h documents only the layout
> of that structure, not its content. Or, we can hope that the SDVO card
> set it up correctly for us (hah).
>
> Intel people, care to shed some light here?
Just re-raising this. I suspect we can't support SDVO LVDS correctly
without knowing more here. In particular:
- what "panel type" means in struct bdb_sdvo_lvds_options
- what the "misc bits" mean in same
- whether the BIOS AIM code can be relied on to have set
depth/type/channel correctly or if that's the driver's job
- ajax
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-10-26 14:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 9:08 Where is SDVO mode setting code in kernel module sources? 4ernov
2011-10-19 13:39 ` Adam Jackson
2011-10-19 13:48 ` 4ernov
2011-10-19 14:28 ` Adam Jackson
2011-10-19 14:43 ` 4ernov
2011-10-19 15:02 ` Adam Jackson
2011-10-19 15:21 ` 4ernov
2011-10-26 14:53 ` Adam Jackson [this message]
2011-10-27 6:49 ` Dear Intel: please document SDVO LVDS option block 4ernov
2011-11-28 17:28 ` Keith Packard
2011-11-28 18:35 ` Adam Jackson
2011-11-28 18:56 ` 4ernov
2011-11-29 9:30 ` 4ernov
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=1319640791.18349.10.camel@atropine \
--to=ajax@redhat.com \
--cc=4ernov@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
/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