1. 10 9月, 2005 1 次提交
    • 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
  2. 22 6月, 2005 1 次提交
  3. 01 5月, 2005 1 次提交
  4. 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