31 Mar, 2011

1 commit

• 25985edce   Fix common misspellings ... Browse Code »

  Fixes generated by 'codespell' and manually reviewed.

  Signed-off-by: Lucas De Marchi

  Lucas De Marchi

  2011-03-31 22:26:23 +0800  

17 Oct, 2008

1 commit

• 3a568051f   neofb: remove open_lock mutex ... Browse Code »

  Remove mutex from the fb_open/fb_release functions as these operations are
  mutexed at fb layer.

  Signed-off-by: Krzysztof Helt
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Krzysztof Helt

  2008-10-17 02:21:42 +0800  

25 Jul, 2008

1 commit

• c6b044d6b   neofb: drop the xtimings structure ... Browse Code »

  Remove the xtimings structure which only stored some values to be used
  later (mostly once). Calculate and use these values in places they are
  needed.

  Signed-off-by: Krzysztof Helt
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Krzysztof Helt

  2008-07-25 01:47:41 +0800  

13 Feb, 2007

1 commit

• c4f28e54d   [PATCH] Video: fb, add true ref_count atomicity ... Browse Code »

  Some of fb drivers uses atomic_t in bad manner, since there are still some
  race-prone gaps. Use mutexes to protect open/close code sections with
  ref_count testing and finally use simple uint.

  Signed-off-by: Jiri Slaby
  Acked-by: Denis Oliver Kropp
  Cc: James Simmons
  Cc: "Antonino A. Daplas"
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Jiri Slaby

  2007-02-13 01:48:42 +0800  

16 Feb, 2006

1 commit

• 9f672004a   [PATCH] neofb: avoid resetting display config on unblank (v2) ... Browse Code »

  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: Christian Trefzer
  Cc: "Antonino A. Daplas"
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Christian Trefzer

  2006-02-16 07:32:21 +0800  

11 Jan, 2006

1 commit

• 9f19bc56c   [PATCH] fbdev: neofb: Driver cleanups ... Browse Code »

  - remove unneeded casts
  - move memory for pseudo_palette inside struct neofb_par

  Signed-off-by: Antonino Daplas
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Antonino A. Daplas

  2006-01-11 00:01:45 +0800  

17 Apr, 2005

1 commit

• 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

  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!

  Linus Torvalds

  2005-04-17 06:20:36 +0800