1. 03 Jun, 2004 3 commits
    • 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
  2. 02 Jun, 2004 12 commits
  3. 31 May, 2004 12 commits
  4. 01 Jun, 2004 6 commits
  5. 31 May, 2004 7 commits