1. 11 Sep, 2003 13 commits
  2. 10 Sep, 2003 2 commits
    • Andries E. Brouwer's avatar
      [PATCH] another keyboard problem solved · 907e4b7b
      Andries E. Brouwer authored
      A colleague reported that the keyboard of his brandnew laptop
      is dead under 2.6 while 2.4 works.
      
      Now I once wrote
      
        In order to avoid interference between scancode sequences
        or mouse packets and the reponses given to commands,
        the keyboard or mouse should always be disabled before
        giving a command that requires a response, and probably
        enabled afterwards. Some keyboards or mice do the disable
        automatically in this situation, but still require an
        explicit enable afterwards. 
      
      (http://www.win.tue.nl/~aeb/linux/kbd/scancodes-9.html)
      
      This is what happens on this laptop. The routine atkbd_probe()
      probes for a keyboard, and after detecting it, enables it.
      But immediately afterwards the routine atkbd_set_3() reads
      the current scancode set and sets the desired set, and as a
      side effect of these commands, the keyboard gets disabled again.
      
      Thus, the keyboard enable must be moved after all command sending
      has been done.
      
      Now that I patch this area anyway: we are almost always in
      scancode set 2 but send the ATKBD_CMD_SETALL_MB command
      that only works in scancode set 3. At best this is useless.
      At worst it confuses the keyboard. So, I put this command
      in a separate routine and call that only when we really
      are in scancode set 3.
      907e4b7b
    • Linus Torvalds's avatar
      Merge bk://bk.arm.linux.org.uk/linux-2.6-rmk · 71d1c9ff
      Linus Torvalds authored
      into home.osdl.org:/home/torvalds/v2.5/linux
      71d1c9ff
  3. 11 Sep, 2003 1 commit
    • Russell King's avatar
      [ARM] Update SA1111 · ccac8ee2
      Russell King authored
      Combine the two initialisation functions, allow SA1111 to be built
      as a module, and remove a redundant SA1111 function prototype.
      ccac8ee2
  4. 10 Sep, 2003 16 commits
  5. 09 Sep, 2003 8 commits
    • Jens Axboe's avatar
      [PATCH] blk API update (and bug fix) to CDU535 cdrom driver · b11a8558
      Jens Axboe authored
      This is a lot better than what is there know.
      
      From: Felipe W Damasio <felipewd@terra.com.br>
      
       - cli-sti removal
       - blk API update
       - set_current_state
       - Remove 'panic' line.
      
      .. and we can now remove the BROKEN_ON_SMP Kconfig annotation.
      b11a8558
    • Jens Axboe's avatar
      [PATCH] get rid of warning in gscd · ee4cdfcc
      Jens Axboe authored
      From: Stephen Hemminger <shemminger@osdl.org>
      
      Compiler warning due to missing equal sign.
      ee4cdfcc
    • Andrew Morton's avatar
      [PATCH] CPU scheduler CAN_MIGRATE fix · 9e3a8956
      Andrew Morton authored
      From: Andrew Theurer <habanero@us.ibm.com>
      
      This change:
      http://linux.bkbits.net:8080/linux-2.5/diffs/kernel/sched.c@1.202
      
      does not seem to make sense:
      
      #define CAN_MIGRATE_TASK(p,rq,this_cpu)					\
      	((!idle || (jiffies - (p)->last_run > cache_decay_ticks)) &&    \
      		!task_running(rq, p) &&					\
      			cpu_isset(this_cpu, (p)->cpus_allowed))
      
      It should be just the opposite; an idle cpu should be able to have a more
      aggressive steal, and a busy cpu should not.
      9e3a8956
    • Andrew Morton's avatar
      [PATCH] sys_fadvise needs asmlinkage · dd3f51c2
      Andrew Morton authored
      dd3f51c2
    • Andrew Morton's avatar
      [PATCH] Reduce random driver lock contention · c3ee1c75
      Andrew Morton authored
      From: Matt Mackall <mpm@selenic.com>
      
      The new locking in the random driver is consuming 60% of CPU resources in
      Anton's monster power5 boxes.
      
      
      Basically, when the primary pool is 7/8th full, we shut off the firehose
      and go into a trickle mode to keep the pool fresh.  Saves CPU for everyone
      and should make the contention drop off the charts too (though the trickle
      factor might need adjusting again for Origin-class machines).
      c3ee1c75
    • Andrew Morton's avatar
      [PATCH] fix Summit srat.h includes · e623ce48
      Andrew Morton authored
      From: Dave Hansen <haveblue@us.ibm.com>
      
      I was compiling for my plain 'ol PC, and was getting unresolved symbols
      for get_memcfg_from_srat() and get_zholes_size().  The CONFIG_NUMA
      definition right now allows it to be turned on for plain old X86_PC. 
      Does anyone know why this is? 
      
      depends on SMP && HIGHMEM64G &&
                (X86_PC || X86_NUMAQ || X86_GENERICARCH ||
                        (X86_SUMMIT && ACPI && !ACPI_HT_ONLY))
      
      In any case, the summit code incorrectly assumes in at least 2 places
      that NUMA && !NUMAQ means summit.  Someone was evidently trying to cover
      the generic subarch case, but that's already taken care of by the lovely
      config system and CONFIG_ACPI_SRAT.  This patch fixes those assumptions
      and adds a nice little warning for people that try to #include srat.h
      without having srat support turned on.
      e623ce48
    • Andrew Morton's avatar
      [PATCH] mwave locking fixes · 5ee6ddc2
      Andrew Morton authored
      From: Manfred Spraul <manfred@colorfullife.com>
      
      The mwave driver uses a user space daemon for some modem operations. The
      user space daemon calls ioctl(,IOCTL_MW_GET_IPC), and the driver returns
      after an interrupt arrived. The actual wait used
      interruptible_sleep_on(), which can lead to lost wakeups. A local 
      spinlock on the stack is used to close that race, but this is broken on 
      SMP, perhaps even with preempt.
      
      The attached patch fixes that by switching to the normal 
      add_wait_queue/test_if_race_occured/schedule/remove_wait_queue sequence.
      5ee6ddc2
    • Andrew Morton's avatar
      [PATCH] ext3: remove debug code · 712c0c6f
      Andrew Morton authored
      ext3 has fancy test harness code which allows you to simulate crashes (for
      testing recovery).  It will make the underlying disk start ignoring writes a
      specified number of seconds after the mount.
      
      It's inoperative without an additional offline patch anyway, and it's doing
      hacky things which scared Al.  So kill it; I'll maintain it in the separate
      ext3 debug patch.
      712c0c6f