1. 14 3月, 2011 1 次提交
  2. 22 2月, 2011 2 次提交
    • C
      drm/i915: Add a module parameter to ignore lid status · fca87409
      Chris Wilson 提交于
      Seems like we are forever to be cursed with buggy firmware, so allow the
      user to explicitly set the panel connection status.
      
      Of secondary utility for cases where I run laptops with the lid closed,
      but still want to configure the LVDS.
      Signed-off-by: NChris Wilson <chris@chris-wilson.co.uk>
      fca87409
    • I
      drm/i915: Do not handle backlight combination mode specially · 951f3512
      Indan Zupancic 提交于
      The current code does not follow Intel documentation: It misses some things
      and does other, undocumented things. This causes wrong backlight values in
      certain conditions. Instead of adding tricky code handling badly documented
      and rare corner cases, don't handle combination mode specially at all. This
      way PCI_LBPC is never touched and weird things shouldn't happen.
      
      If combination mode is enabled, then the only downside is that changing the
      brightness has a greater granularity (the LBPC value), but LBPC is at most
      254 and the maximum is in the thousands, so this is no real functional loss.
      
      A potential problem with not handling combined mode is that a brightness of
      max * PCI_LBPC is not bright enough. However, this is very unlikely because
      from the documentation LBPC seems to act as a scaling factor and doesn't look
      like it's supposed to be changed after boot. The value at boot should always
      result in a bright enough screen.
      
      IMPORTANT: However, although usually the above is true, it may not be when
      people ran an older (2.6.37) kernel which messed up the LBPC register, and
      they are unlucky enough to have a BIOS that saves and restores the LBPC value.
      Then a good kernel may seem to not work: Max brightness isn't bright enough.
      If this happens people should boot back into the old kernel, set brightness
      to the maximum, and then reboot. After that everything should be fine.
      
      For more information see the below links. This fixes bugs:
      
        http://bugzilla.kernel.org/show_bug.cgi?id=23472
        http://bugzilla.kernel.org/show_bug.cgi?id=25072Signed-off-by: NIndan Zupancic <indan@nul.nu>
      Tested-by: NAlex Riesen <raa.lkml@gmail.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      951f3512
  3. 16 2月, 2011 1 次提交
  4. 13 1月, 2011 1 次提交
  5. 12 1月, 2011 1 次提交
  6. 23 11月, 2010 1 次提交
  7. 21 9月, 2010 1 次提交
  8. 08 9月, 2010 1 次提交
  9. 10 8月, 2010 1 次提交