1. 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
  2. 17 4月, 2005 2 次提交
    • A
      [PATCH] ppc64: remove -fno-omit-frame-pointer · 89e09f5e
      Anton Blanchard 提交于
      During some code inspection using gcc 4.0 I noticed a stack frame was being
      created for a number of functions that didnt require it.  For example:
      
      c0000000000df944 <._spin_unlock>:
      c0000000000df944:       fb e1 ff f0     std     r31,-16(r1)
      c0000000000df948:       f8 21 ff c1     stdu    r1,-64(r1)
      c0000000000df94c:       7c 3f 0b 78     mr      r31,r1
      c0000000000df950:       7c 20 04 ac     lwsync
      c0000000000df954:       e8 21 00 00     ld      r1,0(r1)
      c0000000000df958:       38 00 00 00     li      r0,0
      c0000000000df95c:       90 03 00 00     stw     r0,0(r3)
      c0000000000df960:       eb e1 ff f0     ld      r31,-16(r1)
      c0000000000df964:       4e 80 00 20     blr
      
      It turns out we are adding -fno-omit-frame-pointer to ppc64 which is
      causing the above behaviour.  Removing that flag results in much better
      code:
      
      c0000000000d5b30 <._spin_unlock>:
      c0000000000d5b30:       7c 20 04 ac     lwsync
      c0000000000d5b34:       38 00 00 00     li      r0,0
      c0000000000d5b38:       90 03 00 00     stw     r0,0(r3)
      c0000000000d5b3c:       4e 80 00 20     blr
      
      We dont require a frame pointer to debug on ppc64, so remove it.
      Signed-off-by: NAnton Blanchard <anton@samba.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      89e09f5e
    • 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