1. 11 3月, 2008 1 次提交
  2. 30 11月, 2007 1 次提交
    • H
      x86_64 EFI boot support: EFI frame buffer driver · 7c83172b
      Huang, Ying 提交于
      This patch adds Graphics Output Protocol support to the kernel.  UEFI2.0 spec
      deprecates Universal Graphics Adapter (UGA) protocol and only Graphics Output
      Protocol (GOP) is produced.  Therefore, the boot loader needs to query the
      UEFI firmware with appropriate Output Protocol and pass the video information
      to the kernel.  As a result of GOP protocol, an EFI framebuffer driver is
      needed for displaying console messages.  The patch adds a EFI framebuffer
      driver.  The EFI frame buffer driver in this patch is based on the Intel Mac
      framebuffer driver.
      
      The ELILO bootloader takes care of passing the video information as
      appropriate for EFI firmware.
      
      The framebuffer driver has been tested in i386 kernel and x86_64 kernel on EFI
      platform.
      Signed-off-by: NChandramouli Narayanan <mouli@linux.intel.com>
      Signed-off-by: NHuang Ying <ying.huang@intel.com>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Andi Kleen <ak@suse.de>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      7c83172b
  3. 17 10月, 2007 2 次提交
    • M
      bf54x-lq043fb: framebuffer driver for Blackfin BF54x framebuffer device driver · e9fa7c43
      Michael Hennerich 提交于
      Blackfin BF54x framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
      
      [adaplas]
      Add 'fb' suffix to driver name.
      Move Makefile entry under platform device section
      Signed-off-by: NMichael Hennerich <michael.hennerich@analog.com>
      Signed-off-by: NBryan Wu <bryan.wu@analog.com>
      Signed-off-by: NAntonino Daplas <adaplas@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      e9fa7c43
    • M
      uvesafb: the driver core · 8bdb3a2d
      Michal Januszewski 提交于
      uvesafb is an enhanced version of vesafb.  It uses a userspace helper (v86d)
      to execute calls to the x86 Video BIOS functions.  The driver is not limited
      to any specific arch and whether it works on a given arch or not depends on
      that arch being supported by the userspace daemon.  It has been tested on
      x86_32 and x86_64.
      
      A single BIOS call is represented by an instance of the uvesafb_ktask
      structure.  This structure contains a buffer, a completion struct and a
      uvesafb_task substructure, containing the values of the x86 registers, a flags
      field and a field indicating the length of the buffer.  Whenever a BIOS call
      is made in the driver, uvesafb_exec() builds a message using the uvesafb_task
      substructure and the contents of the buffer.  This message is then assigned a
      random ack number and sent to the userspace daemon using the connector
      interface.
      
      The message's sequence number is used as an index for the uvfb_tasks array,
      which provides a mapping from the messages coming from userspace to the
      in-kernel uvesafb_ktask structs.
      
      The userspace daemon performs the requested operation and sends a reply in the
      form of a uvesafb_task struct and, optionally, a buffer.  The seq and ack
      numbers in the reply should be exactly the same as those in the request.
      
      Each message from userspace is processed by uvesafb_cn_callback() and after
      passing a few sanity checks leads to the completion of a BIOS call request.
      Signed-off-by: NMichal Januszewski <spock@gentoo.org>
      Signed-off-by: NAntonino Daplas <adaplas@gmail.com>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Paulo Marques <pmarques@grupopie.com>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      8bdb3a2d
  4. 01 8月, 2007 1 次提交
  5. 18 7月, 2007 1 次提交
  6. 11 5月, 2007 1 次提交
  7. 10 5月, 2007 3 次提交
  8. 09 5月, 2007 10 次提交
  9. 07 5月, 2007 2 次提交
  10. 05 5月, 2007 1 次提交
  11. 21 2月, 2007 1 次提交
  12. 20 2月, 2007 1 次提交
  13. 13 2月, 2007 4 次提交
  14. 11 12月, 2006 1 次提交
  15. 03 10月, 2006 1 次提交
  16. 01 8月, 2006 1 次提交
  17. 15 7月, 2006 1 次提交
  18. 04 7月, 2006 1 次提交
  19. 27 6月, 2006 2 次提交
  20. 01 4月, 2006 1 次提交
  21. 28 3月, 2006 1 次提交
  22. 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
  23. 30 10月, 2005 1 次提交