1. 10 8月, 2005 1 次提交
  2. 09 8月, 2005 1 次提交
    • A
      [PATCH] nvidiafb: Fix initial display corruption on certain laptops · db6778db
      Antonino Daplas 提交于
      Reported by:Vincent Fortier (Bugzilla Bug 4768)
      
      "At boot time the screen appears moved to the mid right portion of the actual
      video pannel making the end of the line appears at the left edge...  It simply
      looks like moved half way to the right"
      
      His particular hardware has a display with an unusual dimension (1920x1200) but
      unfortunately has no EDID block. None of the entries in the global mode
      database is correct for this particular display, and it particularly has
      difficulty scaling up 640x480 (the default startup mode of nvidiafb) to
      1920x1200 which causes the above described problem.
      
      1, Add 1920x1200 to the global mode database.
      
      2. Let nvidiafb base the startup mode from the flatpanel dimensions only if the
        EDID block is absent, no boot mode parameter is specified by the user, and
        a flatpanel/LCD display is attached.
      Signed-off-by: NAntonino Daplas <adaplas@pol.net>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      db6778db
  3. 07 8月, 2005 1 次提交
  4. 02 8月, 2005 2 次提交
    • A
      [PATCH] tridentfb: Fix scrolling artifacts during disk IO · 8d894c47
      Antonino A. Daplas 提交于
      Reported by: Jochen Hein (Bugzilla Bug 4312)
      
      When there is disk I/O happening, the framebuffer has a little snow on
      the screen.  Once I/O has finished, no garbage remains on screen.
      
      This bug was explained by: Knut Petersen
      
      Most important is CRTC register 2f, signal quality is also improved for
      higher vclk values by changing set_vclk() according to the X drivers and
      cyblafb.c
      
      The fix is to set the performance register (0x2f) with a more stable
      value.
      Signed-off-by: NAntonino Daplas <adaplas@pol.net>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      8d894c47
    • A
      [PATCH] tridentfb: Fix scrolling artifacts if acceleration is enabled · 8dad46cf
      Antonino A. Daplas 提交于
      Reported by: Jochen Hein (Bugzilla Bug 4386)
      
      booting leaves the end of long lines in the last line on screen when
      scrolling.  When X is running, scrolling puts garbage on the screen
      (looks like X data) Console switch fixes the screen.  Behaviour seems to
      be identical with noaccel and without on the video=tridentfb parameter
      in lilo.conf.
      
      This bug was explained by: Knut_Petersen
      
      Acceleration is broken for all BLADE 3D chips for all versions of kernel
      2.6 except for 32bit modes.  Most important reason is that the u32 col
      parameter of the graphics engine needs the color value replicated to all
      u8 of the u32 (8bit modes) and to both u16 of the u32.
      
      Fix color value passed to graphics engine, verified by the reporter.
      Signed-off-by: NAntonino Daplas <adaplas@pol.net>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      8dad46cf
  5. 01 8月, 2005 1 次提交
  6. 30 7月, 2005 2 次提交
  7. 29 7月, 2005 1 次提交
  8. 28 7月, 2005 9 次提交
  9. 18 7月, 2005 1 次提交
  10. 08 7月, 2005 3 次提交
  11. 07 7月, 2005 1 次提交
  12. 30 6月, 2005 1 次提交
  13. 28 6月, 2005 1 次提交
  14. 26 6月, 2005 5 次提交
  15. 24 6月, 2005 1 次提交
  16. 22 6月, 2005 9 次提交