summaryrefslogtreecommitdiffstats
path: root/drivers/video/savage/savagefb_driver.c
diff options
context:
space:
mode:
authorAntonino A. Daplas2005-11-07 10:00:41 +0100
committerLinus Torvalds2005-11-07 16:53:51 +0100
commit1013d26663199f8c1c31e1fe8e9352da09630d69 (patch)
tree51b7a8eb48e553dc514c016a8522d8ac4209bc33 /drivers/video/savage/savagefb_driver.c
parent[PATCH] vesafb: Fix color palette handling (diff)
downloadkernel-qcow2-linux-1013d26663199f8c1c31e1fe8e9352da09630d69.tar.gz
kernel-qcow2-linux-1013d26663199f8c1c31e1fe8e9352da09630d69.tar.xz
kernel-qcow2-linux-1013d26663199f8c1c31e1fe8e9352da09630d69.zip
[PATCH] atyfb: Get initial mode timings from LCD BIOS
Reported by: Jean-Philippe Guérard (Bugzilla Bug 1782) "I've tried with video=atyfb:debug and video=atyfb:debug,mode:1280x600, \ nomtrr. In both case, the screen stays black, but seems divided into 4 vertical bands. Some white lines pop up randomly on each vertical band." The problem is a combination of an incorrect xclk plus lack of timing information. The adapter is attached to an LCD device that can do 1280x600 (which is not a standard resolution). The global mode database does not have an entry for it. Fortunately, the Video BIOS contains the complete timing info for this display, however, atyfb is not making use of it. Add support to get the timing information from the BIOS, if available. Signed-off-by: Antonino Daplas <adaplas@pol.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'drivers/video/savage/savagefb_driver.c')
0 files changed, 0 insertions, 0 deletions