#17008: Testing Rudolf's Intel driver on Thinkpad X220
-------------------------------------------------+-------------------------
Reporter: pulkomandy | Owner: rudolfc
Type: bug | Status: assigned
Priority: normal | Milestone: Unscheduled
Component: | Version: R1/beta2
Drivers/Graphics/intel_extreme/sandybridge |
Resolution: | Keywords:
Blocked By: | Blocking:
Platform: All |
-------------------------------------------------+-------------------------
Comment (by rudolfc):
Pulkomandy, thank you.
Some observations and a question here and there..
- am I correct in believing that the driver looks at the found bios preset
link setup and just uses that? (I think I saw that at least). Anyhow (with
only panel, or with the latest git version at least), FDI link A is used,
with 4 lanes active for your LVDS panel.
- the analog port gets assigned FDI link B which is up I hope (do you see
a icons screen on the analog screen during boot?). Apparantly the
bootscreen on it is max 1024x768 as only a single lane is setup for that
screen.
- this means currently it is not possible to use anything over 1024x768
with that analog connected screen, although if you can set 1280x960 @55Hz
(or even lower) it might 'just' still fit in a single lane. (Seen that
here).
- if you can specify a 1280x1024 or higher bootscreen on the analog screen
though, higher res modes should work I think.
- if the B link is up, looks like it is using 'programmed' filtering
(missing a fixed filter specify, although I am looking at Ivy docs atm).
- Are you able to get a working VGA screen if you select 640, 800 or 1024
mode?
- BTW I did not look at which EDID should be preferred to report from the
driver, personally I would use the lowest common denominator list. I think
at this moment it's not very interesting yet, would be much nicer if
app_server could really handle the two screens seperately ;-)
As a last remark at this moment: I am still working on the FDI link select
stuff to get dualhead working (for most users) and I think that will
happen this week: by using the trick you also used for your panel
(preferred link). After a day's work today I have found it's impossible to
switch over to the other link correctly/reliably currently and I am
assuming this is because we cannot yet successfully do the link train
setup ('full modeswitch').
So I plan to work on modesetting for displayport, and I'll do a try at
getting EDID over the aux port channel (might be though that our 'common'
code really does not support that yet, I have to checkout that code still
though).
After these items I consider my work done more or less on this, and I can
do one more try on the link setup using your gerrit patch in this as well.
Then, it would be nice if someone else took over again on this driver. :)
Thanks for your support!
--
Ticket URL: <https://dev.haiku-os.org/ticket/17008#comment:19>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
