1. 26 Sep, 2005 2 commits
  2. 07 Jul, 2005 1 commit
  3. 23 Jun, 2005 1 commit
    • Daniel Ritz's avatar
      [PATCH] yenta TI: turn off interrupts during card power-on #2 · fa912bcb
      Daniel Ritz authored
      
      
      - make boot-up card recognition more reliable (ie.  redo interrogation
        always if there is no valid 'card inserted' state) (and yes, i saw it
        happening on an o2micro controller that both CB_CBARD and CB_16BITCARD
        bits were set at the same time)
      
      - also redo interrogation before probing the ISA interrupts.  it's safer
        to do the probing with the socket in a clean state.
      
      - make card insert detect more reliable.  yenta_get_status() now returns
        SS_PENDING as long as the card is not completley inserted and one of the
        voltage bits is set.  also !CB_CBARD doesn't mean CB_16BITCARD.  there is
        CB_NOTACARD as well, so make an explicit check for CB_16BITCARD.
      
      - for TI bridges: disable IRQs during power-on.  in all-serial and tied
        interrupt mode the interrupts are always disabled for single-slot
        controllers.  for two-slot contollers the disabling is only done when the
        other slot is empty.  to force disabling there is a new module parameter
        now: pwr_irqs_off=Y (which is a regression for working setups.  that's
        why it's an option, only use when required)
      
      - modparm to disable ISA interrupt probing (isa_probe, defaults to on)
      
      - remove unneeded code/cleanups (ie.  merge yenta_events() into
        yenta_interrupts())
      Signed-off-by: default avatarDaniel Ritz <daniel.ritz@gmx.ch>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      fa912bcb
  4. 05 May, 2005 1 commit
  5. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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