1. 24 6月, 2005 7 次提交
  2. 27 5月, 2005 1 次提交
    • A
      [PATCH] Note on ACPI build fix · 8aadff7d
      Alexander Nyberg 提交于
      Even after the previous fix you can still set CONFIG_ACPI_BOOT
      indirectly even without CONFIG_ACPI by choosing CONFIG_PCI and
      CONFIG_PCI_MMCONFIG.
      
      That doesn't build very well either.
      
      This makes PCI_MMCONFIG depend on ACPI, fixing that hole.
      
      [ I guess in theory Kconfig could follow the whole chain of dependencies
        for things that get selected, but that sounds insanely complicated, so
        we'll just fix up these things by hand.  --Linus ]
      Signed-off-by: NAlexander Nyberg <alexn@telia.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      8aadff7d
  3. 06 5月, 2005 1 次提交
  4. 04 5月, 2005 1 次提交
    • A
      [PATCH] ISA DMA Kconfig fixes - part 1 · 5cae841b
      Al Viro 提交于
      A bunch of drivers use ISA DMA helpers or their equivalents for
      platforms that have ISA with different DMA controller (a lot of ARM
      boxen).  Currently there is no way to put such dependency in Kconfig -
      CONFIG_ISA is not it (e.g.  it is not set on platforms that have no ISA
      slots, but have on-board devices that pretend to be ISA ones).
      
      New symbol added - ISA_DMA_API.  Set when we have functional
      enable_dma()/set_dma_mode()/etc.  set of helpers.  Next patches in the
      series will add missing dependencies for drivers that need them.
      
      I'm very carefully staying the hell out of the recurring flamefest on
      what exactly CONFIG_ISA would mean in ideal world - added symbol has a
      well-defined meaning and for now I really want to treat it as completely
      independent from the mess around CONFIG_ISA.
      Signed-off-by: NAl Viro <viro@parcelfarce.linux.theplanet.co.uk>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      5cae841b
  5. 01 5月, 2005 1 次提交
  6. 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