1. 03 10月, 2006 1 次提交
  2. 01 8月, 2006 1 次提交
  3. 15 7月, 2006 1 次提交
  4. 04 7月, 2006 1 次提交
  5. 27 6月, 2006 2 次提交
  6. 01 4月, 2006 1 次提交
  7. 28 3月, 2006 1 次提交
  8. 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
  9. 30 10月, 2005 1 次提交
  10. 10 9月, 2005 3 次提交
    • A
      [PATCH] s3c2410fb: ARM S3C2410 framebuffer driver · 20fd5767
      Arnaud Patard 提交于
      This set of two patches add support for the framebuffer of the Samsung S3C2410
      ARM SoC.  This driver was started about one year ago and is now used on iPAQ
      h1930/h1940, Acer n30 and probably other s3c2410-based machines I'm not aware
      of.  I've also heard yesterday that it's working also on iPAQ rx3715/rx3115
      (s3c2440-based machines).
      Signed-Off-By: NArnaud Patard <arnaud.patard@rtp-net.org>
      Signed-off-by: NAntonino Daplas <adaplas@pol.net>
      Signed-off-by: NBen Dooks <ben@trinity.fluff.org>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      20fd5767
    • A
      [PATCH] fbdev: Add VESA Coordinated Video Timings (CVT) support · 96fe6a21
      Antonino A. Daplas 提交于
      The Coordinated Video Timings (CVT) is the latest standard approved by VESA
      concerning video timings generation.  It addresses the limitation of GTF which
      is designed mainly for CRT displays.  CRT's have a high blanking requirement
      (as much as 25% of the horizontal frame length) which artificially increases
      the pixelclock.  Digital displays, on the other hand, needs to conserve the
      pixelclock as much as possible.  The GTF also does not take into account the
      different aspect ratios in its calculation.
      
      The new function added is fb_find_mode_cvt().  It is called by fb_find_mode()
      if it recognizes a mode option string formatted for CVT.  The format is:
      
      <xres>x<yres>[M][R][-<bpp>][<at-sign><refresh>][i][m]
      
      The 'M' tells the function to calculate using CVT.  On it's own, it will
      compute a timing for CRT displays at 60Hz.  If the 'R' is specified, 'reduced
      blanking' computation will be used, best for flatpanels.  The 'i' and the 'm'
      is for 'interlaced mode' and 'with margins' respectively.
      
      To determine if CVT was used, check for dmesg for something like this:
      
      CVT Mode - <pix>M<n>[-R], ie: .480M3-R  (800x600 reduced blanking)
      
      where: pix - product of xres and yres, in MB
          M   - is a CVT mode
          n   - the aspect ratio (3 - 4:3; 4 - 5:4; 9 - 16:9, 15:9; A - 16:10)
          -R   - reduced blanking
      Signed-off-by: NAntonino Daplas <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      96fe6a21
    • K
      [PATCH] framebuffer: new driver for cyberblade/i1 graphics core · 9fa68eae
      Knut Petersen 提交于
      This is a framebuffer driver for the Cyberblade/i1 graphics core.
      
      Currently tridenfb claims to support the cyberblade/i1 graphics core.  This
      is of very limited truth.  Even vesafb is faster and provides more working
      modes and a much better quality of the video signal.  There is a great
      number of bugs in tridentfb ...  but most often it is impossible to decide
      if these bugs are real bugs or if fixing them for the cyberblade/i1 core
      would break support for one of the other supported chips.
      
      Tridentfb seems to be unmaintained,and documentation for most of the
      supported chips is not available.  So "fixing" cyberblade/i1 support inside
      of tridentfb was not an option, it would have caused numerous
      if(CYBERBLADEi1) else ...  cases and would have rendered the code to be
      almost unmaintainable.
      
      A first version of this driver was published on 2005-07-31.  A fix for a
      bug reported by Jochen Hein was integrated as well as some changes
      requested by Antonino A.  Daplas.
      
      A message has been added to tridentfb to inform current users of tridentfb
      to switch to cyblafb if the cyberblade/i1 graphics core is detected.
      
      This patch is one logical change, but because of the included documentation
      it is bigger than 70kb.  Therefore it is not sent to lkml and
      linux-fbdev-devel,
      Signed-off-by: NKnut Petersen <Knut_Petersen@t-online.de>
      Cc: Muli Ben-Yehuda <mulix@mulix.org>
      Acked-by: NAntonino Daplas <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9fa68eae
  11. 22 6月, 2005 1 次提交
  12. 01 5月, 2005 1 次提交
  13. 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