1. 27 Oct, 2003 3 commits
  2. 25 Oct, 2003 2 commits
  3. 24 Oct, 2003 2 commits
  4. 25 Oct, 2003 1 commit
  5. 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
  6. 23 Oct, 2003 27 commits
    • David S. Miller's avatar
      Merge nuts.ninka.net:/disk1/davem/BK/sparcwork-2.5 · c1183b09
      David S. Miller authored
      into nuts.ninka.net:/disk1/davem/BK/sparc-2.5
      c1183b09
    • David S. Miller's avatar
    • David Brownell's avatar
      [PATCH] USB: usb enumeration clears full speed ep0 state · c1ac1e59
      David Brownell authored
      This resolves a bug that was recently reported to me by someone
      enumerating a USB 1.1 modem through a high speed hub.  I'm a bit
      surprised we never saw it before; I think cache/dma timings must
      usually be strongly in our favor.
      
      The problem was that the HC was still using the old ep0 maxpacket
      value, so when it received an 18 byte device descriptor it would
      report a packet overrun and enumeration would fail.  The fix is
      straightforward:  invalidate the HC's old endpoint state when we
      change the full speed maxpacket size.  (And eventually, we can
      remove EHCI and OHCI code coping with usbcore not doing this.)
      c1ac1e59
    • Stéphane Eranian's avatar
      [PATCH] ia64: fix critical perfmon2 bugs · 7502ff99
      Stéphane Eranian authored
      This patch fixes the following issues:
      
      - fix a nasty corner case by which a task could inherit psr.pp/psr.up
        that could be stale by the time it runs. psr.pp/psr.up bits must be
        cleared on fork and inherited on execve(). Test case provided by
        John Levon.
      
      - mask interrupts when locking the pfm stat structure. We don't want
        to take PMU interrupts in the middle of this kind of critical
        section.
      
      - fix a bug in pfm_close() for context which use asynchronous
        notifications.  You cannot call fasync_helper() with interrupts
        disabled because it reenables them. There was no real danger of
        moving the call outside our critical section.
      
      - fix a bug in in pfm_flush_pmds() where you can leave the freeze bit
        set in the pmc saved state.
      
      - updated dump_pmu_state()
      
      - cleanup the BUG_ON() usage
      7502ff99
    • Arun Sharma's avatar
      [PATCH] ia64: fix broken __emul_prefix · fe6f0598
      Arun Sharma authored
      his seems to be broken for ia32 on ia64 and possibly other emulation
      architectures as well. The problem comes from
      fs/namei.c:set_fs_altroot() using path_lookup() instead of a
      path_walk() relative to "/" (which is the case for 2.4).
      fe6f0598
    • Greg Kroah-Hartman's avatar
      Merge kroah.com:/home/greg/linux/BK/bleed-2.5 · f1aa095a
      Greg Kroah-Hartman authored
      into kroah.com:/home/greg/linux/BK/usb-2.6
      f1aa095a
    • David Brownell's avatar
      [PATCH] USB: fix usb-storage self-deadlock · fa04f891
      David Brownell authored
      This fixes a problem that showed in usb-storage (osdl bugme 1310)
      and could have shown in other drivers that used usb_reset_device()
      when they already held dev->serialize:  a self-deadlock with some
      devices.
      
      There are some drivers that should likely change so that they grab
      this lock themselves, since they don't call this during probe()
      when the lock is already held.  The lock protects against config
      changes by other tasks, which is currently quite rate.
      fa04f891
    • Alan Stern's avatar
      [PATCH] USB: fix for earlier unusual_devs.h patch · e4a93f13
      Alan Stern authored
      An earlier patch caused trouble because it effectively removed the
      US_FL_FIX_INQUIRY flag for devices with release number higher than
      0x5009.  This one might cause problems because it explicitly goes
      against the immediately preceding comment in unusual_devs.h.  That
      comment says that these Casio digital cameras claim to use the CBI
      transport when in fact they only use CB.  However, there have been two
      reports in the last few weeks from people getting the "unneeded SubClass
      and Protocol" log messages.  One of them was using a device with release
      number 0x1000, right at the start of the range.  The other had a device
      with release number 0x5010, just beyond the end of the current range.
      
      Maybe Casio is marketing two different devices with different behaviors
      but having the same Vendor, Product, and Release values -- I don't know.
      e4a93f13
    • Carsten Busse's avatar
      [PATCH] USB: one more digicam for unusual_devs.h · f1d81bfe
      Carsten Busse authored
      its for the Jenoptik JD 5200 z3 Digicam, to enable it to work as a simple
      storage device
      
      more or less i took the values for the 0x0d96 vendor in the 2.6.0-test7
      usb-storage and mixed them with my device id, which seems to work quite well
      
      tested with 2.4.22 kernel
      f1d81bfe
    • Ian Abbott's avatar
      [PATCH] USB: ftdi_sio - Perle UltraPort new ids - 2 of 2 · 1a301e38
      Ian Abbott authored
      Patch by me (Ian Abbott).  Removed aliases of FTDI_VID define for
      consistency.  Renamed FTDI_PERLE_PID to FTDI_PERLE_ULTRAPORT_PID.
      Removed Matrix Orbital and Perle Systems devices from the 8U232AM
      device table (but left them in the FT232BM device table) as they
      are known to be FT232BM devices.
      1a301e38
    • Ian Abbott's avatar
      [PATCH] USB: ftdi_sio - Perle UltraPort new ids - 1 of 2 · 4b916150
      Ian Abbott authored
      Scott Allen's patch to add vid/pid support for Perle Systems
      UltraPort USB serial converter, merged up with minor whitespace
      changes by myself (Ian Abbott).
      4b916150
    • David Brownell's avatar
      [PATCH] USB: ACM USB modem fixes · b9559928
      David Brownell authored
      Please merge this patch.  I've had two success reports from it.
      Putback comment can be:
      
        Fixes some long-standing cdc-acm bugs including:
        - Oopsing
        - Probe messages not so excessive
        - Makes /proc/bus/usb/devices show both interface claims
        - Now cdc_acm won't hotplug for Ethernet devices (or RNDIS)
      b9559928
    • David T. Hollis's avatar
      [PATCH] USB: ax8817x fixes in usbnet.c · e844f7d3
      David T. Hollis authored
      * ax8817x_set_multicast - use address of dev->data, not contents
      * ax8817x_write_async_cmd - free request and urb if submit fails
      e844f7d3
    • Arnaldo Carvalho de Melo's avatar
      [PATCH] leaking info on drivers/usb · 77974fc2
      Arnaldo Carvalho de Melo authored
      I'm doing an audit wrt copy_to_user leaking info to userspace, started
      with drivers/usb, please apply.
      77974fc2
    • David Mosberger's avatar
    • Bjorn Helgaas's avatar
      [PATCH] ia64: prevent "dd if=/dev/mem" crash · 973a46c9
      Bjorn Helgaas authored
      The drivers/char/mem.c change was accepted, so here's the
      ia64-specific part.
      973a46c9
    • Linus Torvalds's avatar
      Merge bk://kernel.bkbits.net/lord/xfs-2.6 · 8c8c3970
      Linus Torvalds authored
      into home.osdl.org:/home/torvalds/v2.5/linux
      8c8c3970
    • Stephen Lord's avatar
      Merge ssh://lord@kernel.bkbits.net/xfs-2.6 · a514c6ff
      Stephen Lord authored
      into jen.americas.sgi.com:/src/lord/bitkeeper/xfs-2.6
      a514c6ff
    • Stephen Lord's avatar
      [XFS] Change XFS maintainer · 919b8be6
      Stephen Lord authored
      SGI Modid: 2.5.x-xfs:slinx:160507a
      919b8be6
    • Glen Overby's avatar
      [XFS] xfs_dir2_node_addname_int had reminants of an old block placement · 44a15e43
      Glen Overby authored
      algorithm in it.  The old algorithm appeared to look for the first
      place to put a new data block, and thus a new freespace block (this is
      where the 'foundindex' variable came from).  However, new space in a
      directory is always added at the lowest file offset as determined by
      the extent list.  So this stuff is never used.
      
      I completely ripped out the reminants of the old algorithm, and
      (again) moved the freespace block add code inside the conditional
      where a data block is added.
      
      SGI Modid: 2.5.x-xfs:slinx:159751a
      44a15e43
    • Nathan Scott's avatar
      [XFS] Use an xfs_ino_t to hold the result of inode extraction from a handle,... · 9ad8cada
      Nathan Scott authored
      [XFS] Use an xfs_ino_t to hold the result of inode extraction from a handle, not a possibly 32-bit number
      
      SGI Modid: 2.5.x-xfs:slinx:159943a
      9ad8cada
    • Nathan Scott's avatar
      [XFS] final round of code cleanup, now using 3-clause-bsd in these headers · 258b26be
      Nathan Scott authored
      SGI Modid: 2.5.x-xfs:slinx:159997a
      258b26be
    • Linus Torvalds's avatar
      Merge bk://linux-scsi.bkbits.net/scsi-bugfixes-2.6 · 4b0991ad
      Linus Torvalds authored
      into home.osdl.org:/home/torvalds/v2.5/linux
      4b0991ad
    • Mark Haverkamp's avatar
      [PATCH] Work around aacraid FW problem · e2d02589
      Mark Haverkamp authored
      If you have a 4gig or greater system, some versions of aacraid firmware
      have problems if you set HostPhysMemPages >= 0x100000.  This can
      potentially cause data corruption.  If you have 4gig or greater memory,
      this patch sets the HostPhysMemPages to something that the firmware can
      deal with.
      e2d02589
    • Pat LaVarre's avatar
      [PATCH] SG_SET_RESERVED_SIZE negative oops · d0e5f8c0
      Pat LaVarre authored
      I propose the 2.6.0-test8 two-line patch below to teach
      SG_SET_RESERVED_SIZE to reject a negative size, rather than oops-ing.
      d0e5f8c0
    • Mike Anderson's avatar
      [PATCH] Add release function to sd for scsi_disk structure · f7ad2011
      Mike Anderson authored
      This patch removes the delay in calling device_del on the sdev struct
      device during a surprise removal event. Reference counting functions for
      sd's scsi_disk structure where also added to fix issues of unregistering
      when a sd is open.
      
      I have tested this patch using scsi_debug with differnt combinations of
      adds / removes. I mounted both partitioned and un-partitioned sd disks,
      remove the host, and then did a umount. The ref count debug output shows
      the objects staying in place prior to the umount and cleaning up once
      the umount is called.
      
      This patch fixes an issue with a delayed call of device_del on the
      sdev_gendev struct device.
      	- Remove the delayed call to device_del.
      	- Add kobject to sd scsi_disk structure.
      	- Add release function for scsi_disk kobject.
      	- Add get / put functions for scsi_disk and calls to these
      	  functions.
      
       drivers/scsi/scsi.c       |    4 --
       drivers/scsi/scsi_sysfs.c |    3 --
       drivers/scsi/sd.c         |   63 ++++++++++++++++++++++++++++++++++++++++------
       3 files changed, 57 insertions(+), 13 deletions(-)
      f7ad2011
    • Linus Torvalds's avatar
      Make yenta allocate IO resource windows in same range as in 2.4.x · d1d8f3b6
      Linus Torvalds authored
      Apparently some laptops (Compaq EVO N620c for one) have something
      hidden at IO port range 0x1000, and the 2.4.x default of allocating
      IO starting at 0x4000 is safer.
      d1d8f3b6