<div class="gmail_quote">2011/11/28 4ernov <span dir="ltr"><<a href="mailto:4ernov@gmail.com">4ernov@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div><div class="h5">2011/11/28 Adam Jackson <span dir="ltr"><<a href="mailto:ajax@redhat.com" target="_blank">ajax@redhat.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 11/28/11 12:28 PM, Keith Packard wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, 26 Oct 2011 10:53:11 -0400, Adam Jackson<<a href="mailto:ajax@redhat.com" target="_blank">ajax@redhat.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, 2011-10-19 at 10:28 -0400, Adam Jackson wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I assume the SDVO LVDS options block in the VBT would tell us what bits<br>
are correct to program here, but intel_bios.h documents only the layout<br>
of that structure, not its content. Or, we can hope that the SDVO card<br>
set it up correctly for us (hah).<br>
<br>
Intel people, care to shed some light here?<br>
</blockquote>
<br>
Just re-raising this. I suspect we can't support SDVO LVDS correctly<br>
without knowing more here. In particular:<br>
<br>
- what "panel type" means in struct bdb_sdvo_lvds_options<br>
</blockquote>
<br>
Which of the four panels in the SDVO info is actually connected.<br>
</blockquote>
<br></div>
Thank you for this! Let's see if we can figure the rest of this out.<br>
<br>
4ernov, can you build a kernel with the following patch added:<br>
<br>
<a href="http://lists.freedesktop.org/archives/intel-gfx/2011-November/013662.html" target="_blank">http://lists.freedesktop.org/<u></u>archives/intel-gfx/2011-<u></u>November/013662.html</a><br>
<br>
and boot with drm.debug=0x4, and attach dmesg from running it? Also, describe your configuration more exactly; it's clear from older emails from you that you have two SDVO LVDS, but are they the same resolution?<br>
</blockquote></div></div><div><br>Thanks, Keith and Adam.<br><br>Yes, I hope I'll have the result tomorrow. Adam, according to the patch the information you want is an output from SDVO_CMD_GET_LVDS_PANEL_INFORMATION. If it's right I can post it tomorrow morning as I've already printed it after you suggested me this command. I should also say that SDVO_CMD_SET_LVDS_PANEL_INFORMATION is also work: I sent a byte to force 24-bit LVDS mode and it was set properly.<br>
<br>As of configuration: yes, there're two monitors with the same resolution, 800x600@60Hz, connected via 24-bit LVDS (AFAIK SPWG format) to i945GME chipset through Chrontel SDVO converters<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:blue"></span>. As I said before, unfortunately, current BIOS doesn't support OpRegion so it seems there's no access to VBT.<br>
<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
- ajax<br>
</blockquote></div><br>
</blockquote></div><br>Hello,<br>syslog of patched kernel (it was 2.6.36) is attached, it's so long, I think it's not good to paste it to the letter.<br><br>Unfortunately, the command in patch isn't executed, it seems to return earlier, but as I said, I've got the results of SDVO_CMD_GET_LVDS_PANEL_INFORMATION which I gathered before. They are:<br>
0x01 for SDVO_B<br>0x00 for SDVO_C<br>After I set 24-bit mode bit the value for SDVO_C become 0x01, too.<br>