1. 19 3月, 2010 1 次提交
  2. 16 8月, 2008 1 次提交
  3. 01 6月, 2007 1 次提交
    • J
      ALPHA: support graphics on non-zero PCI domains · 025a2215
      Jay Estabrook 提交于
      This code replaces earlier and incomplete handling of graphics on non-zero PCI
      domains (aka hoses or peer PCI buses).
      
      An option (CONFIG_VGA_HOSE) is set TRUE if configuring a GENERIC kernel, or a
      kernel for MARVEL, TITAN, or TSUNAMI machines, as these are the machines whose
      SRM consoles are capable of configuring and handling graphics options on
      non-zero hoses.  All other machines have the option set FALSE.
      
      A routine, "find_console_vga_hose()", is used to find the graphics device
      which the machine's firmware believes is the console device, and it sets a
      global (pci_vga_hose) for later use in managing access to the device.  This is
      called in "init_arch" on TITAN and TSUNAMI machines; MARVEL machines use a
      custom version of this routine because of extra complexity.
      
      A routine, "locate_and_init_vga()", is used to find the graphics device and
      set a global (pci_vga_hose) for later use in managing access to the device, in
      the case where "find_console_vga_hose" has failed.
      
      Various adjustments are made to the ioremap and ioportmap routines for
      detecting and translating "legacy" VGA register and memory references to the
      real PCI domain.
      
      [akpm@linux-foundation.org: don't statically init bss]
      [akpm@linux-foundation.org: build fix]
      Signed-off-by: NJay Estabrook <jay.estabrook@hp.com>
      Signed-off-by: NIvan Kokshaysky <ink@jurassic.park.msu.ru>
      Cc: Richard Henderson <rth@twiddle.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      025a2215
  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