1. 12 3月, 2006 1 次提交
  2. 15 1月, 2006 1 次提交
  3. 11 1月, 2006 1 次提交
  4. 16 12月, 2005 1 次提交
  5. 10 11月, 2005 1 次提交
  6. 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
  7. 06 11月, 2005 1 次提交
    • R
      [DRIVER MODEL] Fix arcfb · 8d972a96
      Russell King 提交于
      Release code in driver modules is a potential cause of oopsen.
      The device may be in use by a userspace process, which will keep
      a reference to the device.  If the module is unloaded, the module
      text will be freed.  Subsequently, when the last reference is
      dropped, the release code will be called, which no longer exists.
      
      Use generic platform device allocation/release code in modules.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Acked-by: NGreg Kroah-Hartman <gregkh@suse.de>
      8d972a96
  8. 30 10月, 2005 1 次提交
  9. 22 6月, 2005 1 次提交