1. 07 1月, 2009 1 次提交
  2. 17 10月, 2008 3 次提交
  3. 25 7月, 2008 3 次提交
  4. 07 2月, 2008 1 次提交
  5. 17 10月, 2007 1 次提交
  6. 31 5月, 2007 1 次提交
  7. 09 5月, 2007 1 次提交
  8. 13 2月, 2007 2 次提交
  9. 09 12月, 2006 1 次提交
  10. 11 7月, 2006 1 次提交
  11. 01 7月, 2006 1 次提交
  12. 27 6月, 2006 1 次提交
    • C
      [PATCH] neofb: fix unblank logic interfering with lid toggled backlight · 4efefd1d
      Christian Trefzer 提交于
      This is a fix for the most annoying problem that remained with neofb:
      
      After "setterm -powersave powerdown" the console blanker will disable the
      backlight after the given timeout expires.  If this happens after the lid
      has been shut, we read "LCD off" from the register and store that in the
      driver.  Once the lid is opened, the backlight turns on, but any key press
      that would awaken the blanked console will switch the backlight off again.
      
      The workaround so far was to use the "display config toggle" Fn key combo -
      once if no external display is attached, otherwise as often as required to
      restore the desired display setup.
      
      The following patch fixes the issue at least for the LCD-only case, with no
      external monitor attached.  Other display setup permutations are pending
      further testing, but so far I can guarantee at least no negative change in
      behaviour, if any at all.
      Signed-off-by: NChristian Trefzer <ctrefzer@gmx.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4efefd1d
  13. 28 3月, 2006 1 次提交
  14. 12 3月, 2006 1 次提交
  15. 16 2月, 2006 1 次提交
    • C
      [PATCH] neofb: avoid resetting display config on unblank (v2) · 9f672004
      Christian Trefzer 提交于
      There were two mistakes in the register-read-on-(un)blank approach.
      
      - First, without proper register (un)locking the value read back will always
        be zero, and this is what I missed entirely until just now.  Due to this,
        the logic could not be verified at all and I tried some bogus checks which
        are completely stupid.
      
      - Second, the LCD status bit will always be set to zero when the backlight
        has been turned off.  Reading the value back during unblank will disable the
        LCD unconditionally, regardless of the state it is supposed to be in, since
        we set it to zero beforehand.
      
      So this is what we do now:
      
      - create a new variable in struct neofb_par, and use that to determine
        whether to read back registers (initialized to true)
      
      - before actually blanking the screen, read back the register to sense any
        possible change made through Fn key combo
      
      - use proper neoUnlock() / neoLock() to actually read something
      
      - every call to neofb_blank() determines if we read back next time: blanking
        disables readback, unblanking (FB_BLANK_UNBLANK) enables it
      
      This should give us a nice and clean state machine.  Has been thoroughly
      tested on a Dell Latitude CPiA / NM220 Chip docked to a C/Dock2 with attached
      CRT in all possible combinations of LCD/CRT on/off.  I changed the config via
      Fn key, let the console blank, unblanked by keypress - works flawlessly.
      Signed-off-by: NChristian Trefzer <ctrefzer@gmx.de>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9f672004
  16. 15 2月, 2006 1 次提交
    • C
      [PATCH] neofb: avoid resetting display config on unblank · 10ee39fe
      Christian Trefzer 提交于
      Fix issues with the NeoMagic framebuffer driver.
      
      It nicely complements my previous fix already in linus' tree.  The only
      thing missing now is that the external CRT will not be activated at neofb
      init when external-only is selected, either by register read or
      module/kernel parameter.
      
      Testing was done on a Dell Latitude CPi-A/NM2200 chip.
      
      Previous behaviour:
      - before booting linux, set the preferred display config X via FN+F8
      
      - boot linux, neofb stores the register values in a private
        variable
      
      - change the display config to Y via keystroke
      
      - leave the machine in peace until display is blanked
      
      - touching any key will result in display config X being restored
      
      - booting up, the BIOS will acknowledge config Y, though...
      
      Current behaviour:
      At the time of unblanking, config Y is honoured because we now read back
      register contents instead of just overwriting them with outdated values.
      
      Signed-off by: Christian Trefzer <ctrefzer@gmx.de>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      10ee39fe
  17. 15 1月, 2006 1 次提交
    • C
      [PATCH] neofb: take existing display configuration as default · 4836f574
      Christian Trefzer 提交于
      On a Dell Latitude CPi-A I noticed a strangeness wrt.  the handling of an
      external monitor by the neomagic framebuffer driver, namely when the laptop is
      docked in a C/Dock II with the lid shut.
      
      A cold boot would result in the BIOS configuring the video chip to use the
      "external monitor only" mode, yet neofb would default to "internal LCD only".
      An attempt for a quick fix by using the Fn-F8 keystroke to toggle the display
      combination modes resulted in a reproductible hard lock, powering down being
      the only solution.
      
      The attached patch makes neofb probe the register for the current display
      mode, using that value as a default if nothing was specified as kernel/module
      parameter.
      Signed-off-by: NAntonino Daplas <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4836f574
  18. 11 1月, 2006 1 次提交
  19. 07 11月, 2005 1 次提交
    • A
      [PATCH] fbcon/fbdev: Move softcursor out of fbdev to fbcon · c465e05a
      Antonino A. Daplas 提交于
      According to Jon Smirl, filling in the field fb_cursor with soft_cursor for
      drivers that do not support hardware cursors is redundant.  The soft_cursor
      function is usable by all drivers because it is just a wrapper around
      fb_imageblit.  And because soft_cursor is an fbcon-specific hook, the file is
      moved to the console directory.
      
      Thus, drivers that do not support hardware cursors can leave the fb_cursor
      field blank.  For drivers that do, they can fill up this field with their own
      version.
      
      The end result is a smaller code size.  And if the framebuffer console is not
      loaded, module/kernel size is also reduced because the soft_cursor module will
      also not be loaded.
      Signed-off-by: NAntonino Daplas <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      c465e05a
  20. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4