1. 29 7月, 2009 1 次提交
  2. 20 6月, 2009 6 次提交
  3. 17 6月, 2009 1 次提交
    • D
      Staging: Add octeon-ethernet driver files. · 80ff0fd3
      David Daney 提交于
      The octeon-ethernet driver supports the sgmii, rgmii, spi, and xaui
      ports present on the Cavium OCTEON family of SOCs.  These SOCs are
      multi-core mips64 processors with existing support over in arch/mips.
      
      The driver files can be categorized into three basic groups:
      
      1) Register definitions, these are named cvmx-*-defs.h
      
      2) Main driver code, these have names that don't start cvmx-.
      
      3) Interface specific functions and other utility code, names starting
      with cvmx-
      Signed-off-by: NDavid Daney <ddaney@caviumnetworks.com>
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      80ff0fd3
  4. 15 6月, 2009 1 次提交
    • J
      drm/radeon: introduce kernel modesetting for radeon hardware · 771fe6b9
      Jerome Glisse 提交于
      Add kernel modesetting support to radeon driver, use the ttm memory
      manager to manage memory and DRM/GEM to provide userspace API.
      In order to avoid backward compatibility issue and to allow clean
      design and code the radeon kernel modesetting use different code path
      than old radeon/drm driver.
      
      When kernel modesetting is enabled the IOCTL of radeon/drm
      driver are considered as invalid and an error message is printed
      in the log and they return failure.
      
      KMS enabled userspace will use new API to talk with the radeon/drm
      driver. The new API provide functions to create/destroy/share/mmap
      buffer object which are then managed by the kernel memory manager
      (here TTM). In order to submit command to the GPU the userspace
      provide a buffer holding the command stream, along this buffer
      userspace have to provide a list of buffer object used by the
      command stream. The kernel radeon driver will then place buffer
      in GPU accessible memory and will update command stream to reflect
      the position of the different buffers.
      
      The kernel will also perform security check on command stream
      provided by the user, we want to catch and forbid any illegal use
      of the GPU such as DMA into random system memory or into memory
      not owned by the process supplying the command stream. This part
      of the code is still incomplete and this why we propose that patch
      as a staging driver addition, future security might forbid current
      experimental userspace to run.
      
      This code support the following hardware : R1XX,R2XX,R3XX,R4XX,R5XX
      (radeon up to X1950). Works is underway to provide support for R6XX,
      R7XX and newer hardware (radeon from HD2XXX to HD4XXX).
      
      Authors:
          Jerome Glisse <jglisse@redhat.com>
          Dave Airlie <airlied@redhat.com>
          Alex Deucher <alexdeucher@gmail.com>
      Signed-off-by: NJerome Glisse <jglisse@redhat.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      Signed-off-by: NAlex Deucher <alexdeucher@gmail.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      771fe6b9
  5. 04 4月, 2009 11 次提交
  6. 30 3月, 2009 1 次提交
  7. 19 3月, 2009 1 次提交
  8. 07 1月, 2009 16 次提交
  9. 18 12月, 2008 1 次提交
  10. 10 11月, 2008 1 次提交
    • L
      Don't ask twice about not including staging drivers · 43e61711
      Linus Torvalds 提交于
      The "Exclude staging drivers" question is there so that we don't build
      staging drivers for allyesconfig or allnoconfig settings, but it's very
      irritating when you've already said "no" to staging drivers earlier.
      
      There is absolutely no point in declining twice - once you've declined
      the staging drivers, you're done.
      
      So make the second question depend on the first question having been
      answered in the affirmative.
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      43e61711