1. 26 4月, 2007 1 次提交
  2. 24 4月, 2007 1 次提交
  3. 29 3月, 2007 1 次提交
  4. 27 3月, 2007 1 次提交
    • D
      [VIDEO] ffb: Fix two DAC handling bugs. · 37db9a34
      David S. Miller 提交于
      The determination of whether the DAC has inverted cursor logic is
      broken, import the version checks the X.org driver uses to fix this.
      
      Next, when we change the timing generator, borrow code from X.org that
      does 10 NOP reads of the timing generator register afterwards to make
      sure the video-enable transition occurs cleanly.
      
      Finally, use macros for the DAC registers and fields in order to
      provide documentation for the next person who reads this code.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      37db9a34
  5. 24 3月, 2007 1 次提交
  6. 23 3月, 2007 1 次提交
  7. 17 3月, 2007 4 次提交
  8. 15 3月, 2007 1 次提交
  9. 10 3月, 2007 2 次提交
  10. 08 3月, 2007 1 次提交
  11. 07 3月, 2007 3 次提交
  12. 06 3月, 2007 1 次提交
  13. 05 3月, 2007 4 次提交
  14. 03 3月, 2007 1 次提交
    • D
      [RADEON]: Fix blanking return value. · 7ab87670
      David S. Miller 提交于
      If you'll recall, over a year ago, I pointed out that the current
      Radeon driver erroneously returns -EINVAL for valid blanking codes,
      here is a link to that thread:
      
      	http://lkml.org/lkml/2006/1/28/6
      
      No other driver does this, and it confuses the X server into thinking
      that the device does not support blanking properly.
      
      I looked again and there is simply no reason for the Radeon driver to
      return -EINVAL for FB_BLANK_NORMAL.  It claims it wants to do this in
      order to convince fbcon to blank in software, right here:
      
      			if (fb_blank(info, blank))
      				fbcon_generic_blank(vc, info, blank);
      
      to software blank the screen.  But it only causes that to happen
      in the FB_BLANK_NORMAL case.
      
      That makes no sense because the Radeon code does this:
      
      		val |= CRTC_DISPLAY_DIS;
      
      in the FB_BLANK_NORMAL case so should be blanking the hardware, and
      there is therefore no reason to SW blank by returning -EINVAL.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      Acked-by: NAntonino Daplas <adaplas@gmail.com>
      7ab87670
  15. 02 3月, 2007 2 次提交
  16. 27 2月, 2007 1 次提交
    • O
      [PATCH] Fix build-failure in drivers/video/s3fb.c · 62fa4dc7
      Ondrej Zajicek 提交于
      Toralf Förster pointed out that drivers/video/s3fb.c would fail to compile:
      > ...
      >   CC      drivers/video/s3fb.o
      > drivers/video/s3fb.c: In function `s3_pci_remove':
      > drivers/video/s3fb.c:1003: warning: unused variable `par'
      > drivers/video/s3fb.c: In function `s3fb_setup':
      > drivers/video/s3fb.c:1141: error: `mtrr' undeclared (first use in this function)
      > drivers/video/s3fb.c:1141: error: (Each undeclared identifier is reported only once
      > drivers/video/s3fb.c:1141: error: for each function it appears in.)
      > make[2]: *** [drivers/video/s3fb.o] Error 1
      > make[1]: *** [drivers/video] Error 2
      > make: *** [drivers] Error 2
      
      Here is fix, it also fixes broken boot options.
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      62fa4dc7
  17. 21 2月, 2007 2 次提交
  18. 20 2月, 2007 12 次提交