1. 04 Jun, 2004 3 commits
  2. 03 Jun, 2004 4 commits
    • Greg Kroah-Hartman's avatar
      USB: remove "devfs" message from kernel log for usb-serial driver · db9efa92
      Greg Kroah-Hartman authored
      No one uses devfs on 2.6 :)
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      db9efa92
    • Scott Cytacki's avatar
      [PATCH] USB: kyocera 7135 patch · 8c670784
      Scott Cytacki authored
      Here is a patch based on 2.6.7-rc2 that makes the Kyocera 7135 work.
      The Kyocera appears to have the same setup as the Trio.  Its endpoints
      are laid out like this:
      
      > >>>type                  address
      > >>>usb bulk out:         0x01
      > >>>usb interrupt in:     0x82
      > >>>usb bulk out:         0x03
      > >>>usb bulk in:          0x84
      The last two are the ones used for the syncing communication.
      
      So the patch adds the ids for the kyocera and makes the treo_attach
      function handle the kyocera too.  I also changed the comment; it appears
      there was an error in the original comment about the treo:
      
      Joe Nardelli wrote:
      > Actually, the comment isn't quite right for Treos either (oops).  It
      > should read:
      >
      > ...
      > 1st bulk in endpoint to communicate with the 2nd bulk out endpoint
      > ...
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      8c670784
    • Alan Stern's avatar
      [PATCH] USB: 2.6-BK usb (printing) broken · b39c9f7e
      Alan Stern authored
      On Sat, 29 May 2004, Jens Axboe wrote:
      
      > > > Both 2.6.7-rc1 and BK current spit out a bunch of:
      > > >
      > > > drivers/usb/class/usblp.c: usblp1: nonzero read/write bulk status received: -2
      > > > drivers/usb/class/usblp.c: usblp1: error -2 reading from printer
      > > > drivers/usb/class/usblp.c: usblp1: error -115 reading from printer
      > > > drivers/usb/class/usblp.c: usblp1: error -115 reading from printer
      > > > ...
      > > >
      > > > (about ~80 of that last line) but work for me.
      
      > Sorry wasn't quite clear - the above messages are with 2.6.7-rc1 and
      > current bk with your patch backed out. Current bk with the patch reports
      > only the timeouts I originally listed.
      
      Okay, I feel better.
      
      It looks like those errors you see are caused by a bug in the usblp
      driver.  The patch below ought to help.
      b39c9f7e
    • Greg Kroah-Hartman's avatar
      Cset exclude: vojtech@suse.cz|ChangeSet|20040602201956|45549 · 55869302
      Greg Kroah-Hartman authored
      Oops, this broke device removal pretty badly :(
      Signed-off-by: default avatarGreg Kroah-Hartman <greg@kroah.com>
      55869302
  3. 02 Jun, 2004 12 commits
  4. 31 May, 2004 12 commits
  5. 01 Jun, 2004 6 commits
  6. 31 May, 2004 3 commits
    • Marcel Holtmann's avatar
      [Bluetooth] Move function exports out of syms.c · 784d9e34
      Marcel Holtmann authored
      With Linux 2.6 there is no need to keep the function exports in a
      central file and thus the use of syms.c makes no real sense. Remove
      it and add the EXPORT_SYMBOL calls to the functions they belong to.
      784d9e34
    • Linus Torvalds's avatar
      Merge bk://bk.arm.linux.org.uk/linux-2.6-pcmcia · 77882f74
      Linus Torvalds authored
      into ppc970.osdl.org:/home/torvalds/v2.6/linux
      77882f74
    • Russell King's avatar
      [PCMCIA] Fix up SOC PCMCIA socket timing calculations · 62bab380
      Russell King authored
      The timing calculations used by the PXA platforms did not always take
      account of the timings handed to us by PCMCIA, and where it did, it
      assumed IO timings for memory windows.
      
      We fix this, and provide a generic function which calculates the
      required timings (in nanoseconds) for IO, memory and attribute
      windows.  The SOC drivers only have to convert this information to
      whatever format the hardware requires to achieve at least these
      timing parameters.
      62bab380