Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Jackson <ajax@redhat.com>
To: 4ernov <4ernov@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Where is SDVO mode setting code in kernel module sources?
Date: Wed, 19 Oct 2011 11:02:46 -0400	[thread overview]
Message-ID: <1319036566.12938.19.camel@atropine> (raw)
In-Reply-To: <CAL8gro3-8CYsD5bG_15Uo83=Fwk9-DVmi_ihOJ+G2d8K6dN--g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1031 bytes --]

On Wed, 2011-10-19 at 18:43 +0400, 4ernov wrote:

> And is it guessed somewhere in case of VBT missing?

Well, not yet, no.  Like I said, there's no code at all yet for tweaking
SDVO LVDS.

> In my case there's
> no OpRegion support (i945GME chipset don't support it as mainboard
> manufacturer informed)

This is, at best, stretching the truth.

> thus there're only "*ERROR* VBT signature
> missing" and "failed to find VBIOS tables" messages printed and I
> think the module doesn't use VBT after this.

I suppose in this case you'd have to hope that the SDVO init code at
POST time set up the device correctly, so that if you called
SDVO_CMD_GET_LVDS_PANEL_INFORMATION it'd tell you the truth.  But that
assumes that the SDVO init code does that, and it might not, I don't
actually know; Intel doesn't release the docs for that publicly (or even
under NDA unless you're an OEM).

That or we'd need to add a way of passing in a VBT from the kernel
command line, like ACPI DSDT override does.

- 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

  reply	other threads:[~2011-10-19 15:02 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 [this message]
2011-10-19 15:21           ` 4ernov
2011-10-26 14:53       ` Dear Intel: please document SDVO LVDS option block Adam Jackson
2011-10-27  6:49         ` 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=1319036566.12938.19.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