1. 27 Oct, 2003 3 commits
    • Linus Torvalds's avatar
      Merge bk://kernel.bkbits.net/davem/net-2.5 · b0200965
      Linus Torvalds authored
      into home.osdl.org:/home/torvalds/v2.5/linux
      b0200965
    • Kevin Corry's avatar
      [PATCH] Fix DM on top of raid · 25f532b9
      Kevin Corry authored
      Force Device-Mapper to use PAGE_SIZE or smaller I/O when the underlying
      device has a bvec_merge_fn routine registered.  This will fix the
      situation of Device-Mapper submitting I/Os to RAID-0 that span the
      RAID-0 chunk boundaries.
      
      Joe is working on a better solution that actually honors the MD
      merge_bvec_fn routine.  But this minimal change will fix the problem for
      the time being.
      25f532b9
    • Linus Torvalds's avatar
      Put the compiler barrier() on the right side of the preemption · 1290f52b
      Linus Torvalds authored
      enable on UP-PREEMPT.
      
      Without this, the enable could "migrate" up into the critical
      region (on SMP, the actual spinlock would act as an additional
      barrier and PREEMPT was ok).
      1290f52b
  2. 26 Oct, 2003 22 commits
  3. 25 Oct, 2003 2 commits
  4. 24 Oct, 2003 6 commits
  5. 25 Oct, 2003 1 commit
  6. 24 Oct, 2003 5 commits
    • Knut Petersen's avatar
      [PATCH] setkeycode ioctl fix · 99438d1e
      Knut Petersen authored
      This is a bugfix for setkeycode() in /drivers/char/keyboard.c.
      
      If we change a keycode the corresponding bit should be cleared if and
      only if this keycode is not defined any longer.  I believe that this
      also was intended with the original code, but the implementation is
      faulty.
      
      First off all the first three changed lines are obviously erroneus:
      oldkey == truekey is false or true, you do not need to inclose this in a
      for().  I believe the author intended INPUT_KEYCODE(dev,i) == oldkey.
      But fixing this alone is not enough.
      
      If somebody wants to interchange the definition of two keys A and B, the
      normal way is to use two setkeycode calls:
      
          setkeycode (scancode A, keycode B);
          setkeycode (scancode B, keycode A);
      
      The old code does a clearbit(oldkey ..) call even in situations where
      two keys have the same definition, and this situation arises commonly in
      the situation mentioned above.
      
      Both errors are fixed with this patch.
      99438d1e
    • Knut Petersen's avatar
      [PATCH] input / keyboard / Scancode Set 3 support broken · f71a8923
      Knut Petersen authored
      If somebody uses keyboard scancode set 3 it is necessary to explicitly
      program the keyboard to send make/break codes for all keys and to set
      autorepeat for all keys.
      
      This is critical for some people.  One example is the LK461/46W series
      of keyboards from Digital Equipment Corporations.  These are VMS
      keyboards that are also usable on a normal PC.
      
      These keyboards support Scancode Set 2, but for some keys this support
      is screwed up -- some function keys (e.g.  F18/F20) report the same
      scancode sequence combined with both alt and shift keys. 
      
      Scancode Set 3 works perfectly if all keys are programmed to give
      make/break codes. 
      
      A lot of keyboards manufactured by Cherry only make/break for some (not all!)
      modifyer keys in scancode set 3 without this fix.
      f71a8923
    • Linus Torvalds's avatar
      Merge bk://kernel.bkbits.net/gregkh/linux/usb-2.6 · d548fa6f
      Linus Torvalds authored
      into home.osdl.org:/home/torvalds/v2.5/linux
      d548fa6f
    • Linus Torvalds's avatar
      Merge bk://kernel.bkbits.net/davem/sparc-2.5 · 7a2dd9ac
      Linus Torvalds authored
      into home.osdl.org:/home/torvalds/v2.5/linux
      7a2dd9ac
    • Linus Torvalds's avatar
      Add a quirk for the Intel ICH-[45] to add special ACPI regions. · b91728bb
      Linus Torvalds authored
      This fixes resource conflicts due to IO decode that doesn't show
      up with a normal PCI probe (we do similar quirks for most other
      chipsets). Without it, the kernel doesn't know about some magic
      IO decodes for the chips.
      b91728bb
  7. 23 Oct, 2003 1 commit