1. 04 Sep, 2003 2 commits
    • David Brownell's avatar
      [PATCH] USB: usb "gadgetfs" (2/2) · 7c9481c3
      David Brownell authored
      This adds the kconfig/kbuild hooks needed to build
      the driver.
      7c9481c3
    • David Brownell's avatar
      [PATCH] USB: usb "gadgetfs" (1/2) · 80150dc5
      David Brownell authored
      This is another "gadget" driver -- one that lets user mode
      code implement usb device functions, with all the classic
      advantages of such solutions.  There's an example driver
      at the linux-usb "gadget" web page, which uses pthreads
      and handles several control requests in user mode.
      
      This capability is packaged in the form of a filesystem,
      conventionally mounted at /dev/gadget, with files that the
      user mode driver opens, configures, and then uses with
      normal read() and write() system calls.  Because this
      doesn't require use of ioctl(), such user mode drivers
      can be written in almost any language:  not just C, but
      also Java, Python, Perl, and others -- likely even BASH.
      
      For now, such user mode gadget drivers are limited to a
      single configuration, although the interfaces in that
      configuration could support multiple altsettings when
      the hardware allows.
      
      Please merge.  This first patch provides the driver,
      the next one adds kconfig and kbuild support.
      80150dc5
  2. 03 Sep, 2003 1 commit
  3. 02 Sep, 2003 18 commits
    • Greg Kroah-Hartman's avatar
    • Duncan Sands's avatar
      [PATCH] USB: fix uhci "host controller process error" · 235d0690
      Duncan Sands authored
      By the way, let me explain what the problem was with uhci-hcd.  The usb
      hardware directly accesses your computers memory.  The bug is that it
      could still be accessing a bit of memory after uhci-hcd thought it had
      finished with it and freed up the memory.  This bug has always existed,
      and I guess led to occasional mysterious data corruption, when some
      other part of the kernel started using that bit of memory while the usb
      hardware was still playing with it.  You turned on the "slab debugging"
      option, right?  With this turned on, when uhci-hcd frees the memory it
      gets filled with some garbage values.  The usb hardware reads this
      garbage and barfs, giving a "process error".  In short, you can also
      get rid of the process error messages by turning off slab debugging,
      then the data corruption will be silent again!
      235d0690
    • Greg Kroah-Hartman's avatar
      Merge kroah.com:/home/greg/linux/BK/bleed-2.5 · 0bc1a622
      Greg Kroah-Hartman authored
      into kroah.com:/home/greg/linux/BK/gregkh-2.6
      0bc1a622
    • Greg Kroah-Hartman's avatar
      Merge kroah.com:/home/greg/linux/BK/bleed-2.5 · 8427ec15
      Greg Kroah-Hartman authored
      into kroah.com:/home/greg/linux/BK/gregkh-2.6
      8427ec15
    • Linus Torvalds's avatar
      Instead of asking for "broken drivers", ask for a "clean compile". · af8b3563
      Linus Torvalds authored
      This makes "allyesconfig" do a better job.
      af8b3563
    • Linus Torvalds's avatar
      Add the isicom serial driver to the list of drivers that are · a87d6bc0
      Linus Torvalds authored
      broken on SMP (due to expecting global irq locking).
      a87d6bc0
    • Jeff Garzik's avatar
      [PATCH] Fix non-modular compile of 3c515.c · 95bd4d35
      Jeff Garzik authored
      95bd4d35
    • David Brownell's avatar
      [PATCH] USB: usb hcd states · 95ec612c
      David Brownell authored
      AFAICT this is ready for your next merge with Linus.
      
      Ben's ohci stuff was not cooked yet, seemed like the
      pm stuff wasn't yet supporting the hook(s) he needed.
      RMK had similar issues w.r.t. PM on ARM too.
      
      
      This patch includes:
      
         - updates from Benjamin Herrenschmidt to make usbcore
           behave a bit better during PM suspend (setting and
           checking hcd state).
      
         - related updates from me, making more paths into hcds
           fail when the driver is suspended.
      
         - updates based on some feedback from Alan Stern,
           notably including getting rid of a state we don't
           really need (most of the patch, by volume).
      
         - an experiment that tries to give a warning in the
           sadly common case of ACPI or APIC (etc) settings
           that need to change before USB works.
      
      Net effect is that some of the PM issues start to get
      resolved, maybe IRQ problems will be diagnosed quicker,
      and some overdue cleanup gets started.
      95ec612c
    • David Brownell's avatar
      [PATCH] USB: net2280 one-liner · 83744de4
      David Brownell authored
      Please merge this minor fix:
      
         - loosen constraints on buffer allocation
      
      This is needed before Alan's file-backed storage
      gadget driver will initialize using net2280.
      83744de4
    • Alan Stern's avatar
      [PATCH] USB: storage: Revised update to isd200 I/O buffer patch · a4adae52
      Alan Stern authored
      This is a minor revision to the previous patch as83.  It changes the name
      of the various struct hd_driveid variables from 'drive' to 'id', per
      Andries Brouwer's request.
      
       - Don't do DMA into the middle of a structure (info->drive).
       - Don't use I/O buffers for two different purposes simultaneously
       	(info->ATARegs, regs, us->iobuf).
       - Rename info->drive to info->id.
      a4adae52
    • Pat LaVarre's avatar
      [PATCH] USB: storage: cbw/csw trace in order · 0c2dfb88
      Pat LaVarre authored
      Via this patch ...
      
      We change only when CONFIG_USB_STORAGE_DEBUG=y.
      
      To /proc/kmsg etc. we now trace the fields of
      the cbw as we order those fields in ram and as
      we order those fields in time on the bus, to
      avoid disorientating those of us who view those
      canonical orders often.
      
      Also we no longer print "S" or "Sig" to
      "Signature", instead we always print "S".  We
      chose "S" over "Sig" because it is the "T"
      signature (aka "Tag") that actually makes each
      cbw/csw pair distinct, whereas the so-called
      Signatures only distinguish cbw from csw by
      flipping one bit.
      
      Also in the trace we uppercase a 'C' and an 'S'
      to keep cbw from csw typographically distinct.
      
      For example, what was:
      
      <7>usb-storage: Command INQUIRY (6 bytes)
      <7>usb-storage:  12 00 00 00 24 00
      <7>usb-storage: Bulk command S 0x43425355 T 0x1f13 Trg 0 LUN 0 L 36 F 128 CL 6
      ...
      <7>usb-storage: Bulk status Sig 0x53425355 T 0x1f13 R 0 Stat 0x0
      
      becomes:
      
      <7>usb-storage: Command INQUIRY (6 bytes)
      <7>usb-storage:  12 00 00 00 24 00
      <7>usb-storage: Bulk Command S 0x43425355 T 0x1f3b L 36 F 128 Trg 0 LUN 0 CL 6
      ...
      <7>usb-storage: Bulk Status S 0x53425355 T 0x1f3b R 0 Stat 0x0
      0c2dfb88
    • Linus Torvalds's avatar
      Fix keyboard double E0-sequence release case · 96baeca0
      Linus Torvalds authored
      From Andries Brouwer <aebr@win.tue.nl>: we discard the double
      release keypress, but we did it without clearing the "last byte
      was E0" flag. So the next byte in the input stream would get
      corrupted.
      96baeca0
    • Adrian Bunk's avatar
      [PATCH] Mark more drivers BROKEN{,ON_SMP} · 51e9e974
      Adrian Bunk authored
      - let more drivers that don't compile depend on BROKEN
      - MTD_BLKMTD is fixed, remove the dependency on BROKEN
      - let all drivers that don't compile on SMP (due to cli/sti usage)
        depend on a BROKEN_ON_SMP that is only defined if !SMP || BROKEN
      - #include interrupt.h for dummy cli/sti/... in two files to fix the
        UP compilation of these files
      
      I marked only drivers that are broken for a long time and where I don't 
      know about existing fixes with BROKEN or BROKEN_ON_SMP.
      51e9e974
    • Linus Torvalds's avatar
      Merge bk://kernel.bkbits.net/davem/net-2.5 · 596a338d
      Linus Torvalds authored
      into home.osdl.org:/home/torvalds/v2.5/linux
      596a338d
    • Bartlomiej Zolnierkiewicz's avatar
      [PATCH] ide: forward-port siimage driver changes from 2.4.22 · d964d911
      Bartlomiej Zolnierkiewicz authored
      ide: forward-port siimage driver changes from 2.4.22
      d964d911
    • Bartlomiej Zolnierkiewicz's avatar
      [PATCH] ide: fix ide_unregister() vs. driver model · 8fc7b528
      Bartlomiej Zolnierkiewicz authored
      From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      
      This patch seem to have been lost, so here it is again.  It fixes an Ooops
      on unregistering hwifs due to the device model now having mandatory
      release() functions.  It also close the possible race we had on release if
      the entry was in use (by or /sys typically) by using a semaphore waiting
      for the release() to be called after doing an unregister.
      8fc7b528
    • Ben Collins's avatar
      [PATCH] Fix compile for raw1394 · ed2149ac
      Ben Collins authored
      Include vmalloc.h to fix compilation of raw1394.c
      ed2149ac
    • Arnaldo Carvalho de Melo's avatar
      [PATCH] scsi cleanups · 39c743c3
      Arnaldo Carvalho de Melo authored
        o scsi/imm.h: use c99 style initialization
      
        As far as I verified this also fixes a bug when doing the
        table lookup for IMM_EPP_32, that would result in "Unknown"
        as IMM_EPP_32 is equal to 6 and there is the #ifdef...
      
      ChangeSet@1.1386, 2003-09-02 00:11:07-03:00, acme@allegro.kerneljanitors.org
        o scsi/*.h: remove not needed #define NULL
      
      ChangeSet@1.1385, 2003-09-02 00:05:16-03:00, acme@allegro.kerneljanitors.org
        o scsi/3w-xxx.h: use c99 style init
      39c743c3
  4. 01 Sep, 2003 19 commits