1. 06 Mar, 2010 1 commit
  2. 29 Dec, 2009 1 commit
    • Stefan Richter's avatar
      firewire, ieee1394: update Kconfig help · 5d7db049
      Stefan Richter authored
      Update the Kconfig help texts of both stacks to encourage a general move
      from the older to the newer drivers.  However, do not label ieee1394 as
      "Obsolete" yet, as the newer drivers have not been deployed as default
      stack in the majority of Linux distributions yet, and those who start
      doing so now may still want to install the old drivers as fallback for
      unforeseen issues.
      Since Linux 2.6.32, FireWire audio devices can be driven by the newer
      firewire driver stack too, hence remove an outdated comment about audio
      devices.  Also remove comments about library versions since the 2nd
      generation of libraw1394 and libdc1394 is now in common use; details on
      library versions can be read at the wiki link from the help texts.
      Signed-off-by: default avatarStefan Richter <[email protected]>
  3. 15 Dec, 2009 1 commit
  4. 09 Nov, 2009 1 commit
  5. 18 Jun, 2009 1 commit
  6. 17 Jun, 2009 1 commit
  7. 19 Dec, 2008 1 commit
    • Len Brown's avatar
      create drivers/platform/x86/ from drivers/misc/ · 41b16dce
      Len Brown authored
      Move x86 platform specific drivers from drivers/misc/
      to a new home under drivers/platform/x86/.
      The community has been maintaining x86 vendor-specific
      platform specific drivers under /drivers/misc/ for a few years.
      The oldest ones started life under drivers/acpi.
      They moved out of drivers/acpi/ because they don't actually
      implement the ACPI specification, but either simply
      use ACPI, or implement vendor-specific ACPI extensions.
      In the future we anticipate...
      drivers/misc/ will go away.
      other architectures will create drivers/platform/<arch>
      Signed-off-by: default avatarLen Brown <[email protected]>
  8. 28 Oct, 2008 1 commit
  9. 10 Oct, 2008 1 commit
  10. 17 Sep, 2008 1 commit
  11. 30 Apr, 2008 1 commit
  12. 24 Apr, 2008 1 commit
  13. 09 Feb, 2008 1 commit
  14. 05 Feb, 2008 1 commit
  15. 04 Feb, 2008 1 commit
  16. 02 Feb, 2008 1 commit
  17. 30 Jan, 2008 1 commit
  18. 23 Oct, 2007 2 commits
  19. 18 Oct, 2007 1 commit
  20. 16 Oct, 2007 1 commit
    • Shannon Nelson's avatar
      DCA: Add Direct Cache Access driver · 7589670f
      Shannon Nelson authored
      Direct Cache Access (DCA) is a method for warming the CPU cache before data
      is used, with the intent of lessening the impact of cache misses.  This
      patch adds a manager and interface for matching up client requests for DCA
      services with devices that offer DCA services.
      In order to use DCA, a module must do bus writes with the appropriate tag
      bits set to trigger a cache read for a specific CPU.  However, different
      CPUs and chipsets can require different sets of tag bits, and the methods
      for determining the correct bits may be simple hardcoding or may be a
      hardware specific magic incantation.  This interface is a way for DCA
      clients to find the correct tag bits for the targeted CPU without needing
      to know the specifics.
          [Dave Miller] use DEFINE_SPINLOCK()
      Signed-off-by: default avatarShannon Nelson <[email protected]>
      Acked-by: default avatarDavid S. Miller <[email protected]>
      Signed-off-by: default avatarAndrew Morton <[email protected]>
      Signed-off-by: default avatarLinus Torvalds <[email protected]>
  21. 10 Oct, 2007 1 commit
  22. 20 Jul, 2007 1 commit
  23. 19 Jul, 2007 1 commit
  24. 18 Jul, 2007 1 commit
  25. 10 Jul, 2007 2 commits
    • Anton Vorontsov's avatar
      [BATTERY] Universal power supply class (was: battery class) · 4a11b59d
      Anton Vorontsov authored
      This class is result of "external power" and "battery" classes merge,
      as suggested by David Woodhouse. He also implemented uevent support.
      Here how userspace seeing it now:
          	# ls /sys/class/power\ supply/
          	ac  main-battery  usb
          	# cat /sys/class/power\ supply/ac/type
          	# cat /sys/class/power\ supply/usb/type
          	# cat /sys/class/power\ supply/main-battery/type
          	# cat /sys/class/power\ supply/ac/online
          	# cat /sys/class/power\ supply/usb/online
          	# cat /sys/class/power\ supply/main-battery/status
          	# cat /sys/class/leds/h5400\:red-left/trigger
          	none h5400-radio timer hwtimer ac-online usb-online
          	main-battery-charging-or-full [main-battery-charging]
      Signed-off-by: default avatarAnton Vorontsov <[email protected]>
      Signed-off-by: David Woodhouse's avatarDavid Woodhouse <[email protected]>
      Signed-off-by: default avatarAndrew Morton <[email protected]>
    • Jens Axboe's avatar
      Remove legacy CDROM drivers · f3f541f9
      Jens Axboe authored
      They are all broken beyond repair. Given that nobody has complained
      about them (most haven't worked in 2.6 AT ALL), remove them from the
      A new mitsumi driver that actually works is in progress, it'll get
      added when completed.
      Signed-off-by: default avatarJens Axboe <[email protected]>
  26. 09 Mar, 2007 2 commits
  27. 11 Feb, 2007 1 commit
  28. 10 Dec, 2006 1 commit
    • Avi Kivity's avatar
      [PATCH] kvm: userspace interface · 6aa8b732
      Avi Kivity authored
      web site: http://kvm.sourceforge.net
      mailing list: [email protected]
      The following patchset adds a driver for Intel's hardware virtualization
      extensions to the x86 architecture.  The driver adds a character device
      (/dev/kvm) that exposes the virtualization capabilities to userspace.  Using
      this driver, a process can run a virtual machine (a "guest") in a fully
      virtualized PC containing its own virtual hard disks, network adapters, and
      Using this driver, one can start multiple virtual machines on a host.
      Each virtual machine is a process on the host; a virtual cpu is a thread in
      that process.  kill(1), nice(1), top(1) work as expected.  In effect, the
      driver adds a third execution mode to the existing two: we now have kernel
      mode, user mode, and guest mode.  Guest mode has its own address space mapping
      guest physical memory (which is accessible to user mode by mmap()ing
      /dev/kvm).  Guest mode has no access to any I/O devices; any such access is
      intercepted and directed to user mode for emulation.
      The driver supports i386 and x86_64 hosts and guests.  All combinations are
      allowed except x86_64 guest on i386 host.  For i386 guests and hosts, both pae
      and non-pae paging modes are supported.
      SMP hosts and UP guests are supported.  At the moment only Intel
      hardware is supported, but AMD virtualization support is being worked on.
      Performance currently is non-stellar due to the naive implementation of the
      mmu virtualization, which throws away most of the shadow page table entries
      every context switch.  We plan to address this in two ways:
      - cache shadow page tables across tlb flushes
      - wait until AMD and Intel release processors with nested page tables
      Currently a virtual desktop is responsive but consumes a lot of CPU.  Under
      Windows I tried playing pinball and watching a few flash movies; with a recent
      CPU one can hardly feel the virtualization.  Linux/X is slower, probably due
      to X being in a separate process.
      In addition to the driver, you need a slightly modified qemu to provide I/O
      device emulation and the BIOS.
      Caveats (akpm: might no longer be true):
      - The Windows install currently bluescreens due to a problem with the
        virtual APIC.  We are working on a fix.  A temporary workaround is to
        use an existing image or install through qemu
      - Windows 64-bit does not work.  That's also true for qemu, so it's
        probably a problem with the device model.
      [[email protected]: build fix]
      [[email protected]: build fix, other fixes]
      [[email protected]: KVM: Expose interrupt bitmap]
      [[email protected]: i386 build fix]
      [[email protected]: i386 fixes]
      [[email protected]: add log levels to all printks]
      [[email protected]: Fix sparse NULL and C99 struct init warnings]
      [[email protected]: KVM: AMD SVM: 32-bit host support]
      Signed-off-by: default avatarYaniv Kamay <[email protected]>
      Signed-off-by: default avatarAvi Kivity <[email protected]>
      Cc: Simon Kagstrom <[email protected]>
      Cc: Bernhard Rosenkraenzer <[email protected]>
      Signed-off-by: default avatarUri Lublin <[email protected]>
      Cc: Ingo Molnar <[email protected]>
      Cc: Roland Dreier <[email protected]>
      Signed-off-by: default avatarRandy Dunlap <[email protected]>
      Signed-off-by: default avatarAnthony Liguori <[email protected]>
      Signed-off-by: default avatarAndrew Morton <[email protected]>
      Signed-off-by: default avatarLinus Torvalds <[email protected]>
  29. 08 Dec, 2006 1 commit
  30. 17 Oct, 2006 1 commit
  31. 10 Aug, 2006 1 commit
  32. 18 Jun, 2006 1 commit
  33. 21 Apr, 2006 1 commit
  34. 31 Mar, 2006 1 commit
  35. 27 Mar, 2006 1 commit
  36. 19 Jan, 2006 1 commit
  37. 14 Jan, 2006 1 commit
    • David Brownell's avatar
      [PATCH] spi: simple SPI framework · 8ae12a0d
      David Brownell authored
      This is the core of a small SPI framework, implementing the model of a
      queue of messages which complete asynchronously (with thin synchronous
      wrappers on top).
        - It's still less than 2KB of ".text" (ARM).  If there's got to be a
          mid-layer for something so simple, that's the right size budget.  :)
        - The guts use board-specific SPI device tables to build the driver
          model tree.  (Hardware probing is rarely an option.)
        - This version of Kconfig includes no drivers.  At this writing there
          are two known master controller drivers (PXA/SSP, OMAP MicroWire)
          and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
          mentions of other drivers in development.
        - No userspace API.  There are several implementations to compare.
          Implement them like any other driver, and bind them with sysfs.
      The changes from last version posted to LKML (on 11-Nov-2005) are minor,
      and include:
        - One bugfix (removes a FIXME), with the visible effect of making device
          names be "spiB.C" where B is the bus number and C is the chipselect.
        - The "caller provides DMA mappings" mechanism now has kerneldoc, for
          DMA drivers that want to be fancy.
        - Hey, the framework init can be subsys_init.  Even though board init
          logic fires earlier, at arch_init ... since the framework init is
          for driver support, and the board init support uses static init.
        - Various additional spec/doc clarifications based on discussions
          with other folk.  It adds a brief "thank you" at the end, for folk
          who've helped nudge this framework into existence.
      As I've said before, I think that "protocol tweaking" is the main support
      that this driver framework will need to evolve.
      From: Mark Underwood <[email protected]>
        Update the SPI framework to remove a potential priority inversion case by
        reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
      Signed-off-by: default avatarDavid Brownell <[email protected]>
      Signed-off-by: default avatarAndrew Morton <[email protected]>
      Signed-off-by: default avatarGreg Kroah-Hartman <[email protected]>