1. 18 4月, 2008 1 次提交
    • J
      kgdb: add kgdb internal test suite · e8d31c20
      Jason Wessel 提交于
      This patch adds regression tests for testing the kgdb core and arch
      specific implementation.
      
      The kgdb test suite is designed to be built into the kernel and not as
      a module because it uses a number of low level kernel and kgdb
      primitives which should not be exported externally.
      
      The kgdb test suite is designed as a KGDB I/O module which
      simulates the communications that a debugger would have with kgdb.
      The tests are broken up in to a line by line and referenced here as
      a "get" which is kgdb requesting input and "put" which is kgdb
      sending a response.
      
      The kgdb suite can be invoked from the kernel command line
      arguments system or executed dynamically at run time.  The test
      suite uses the variable "kgdbts" to obtain the information about
      which tests to run and to configure the verbosity level.  The
      following are the various characters you can use with the kgdbts=
      line:
      
      When using the "kgdbts=" you only choose one of the following core
      test types:
      A = Run all the core tests silently
      V1 = Run all the core tests with minimal output
      V2 = Run all the core tests in debug mode
      
      You can also specify optional tests:
      N## = Go to sleep with interrupts of for ## seconds
            to test the HW NMI watchdog
      F## = Break at do_fork for ## iterations
      S## = Break at sys_open for ## iterations
      
      NOTE: that the do_fork and sys_open tests are mutually exclusive.
      
      To invoke the kgdb test suite from boot you use a kernel start
      argument as follows:
      	kgdbts=V1 kgdbwait
      Or if you wanted to perform the NMI test for 6 seconds and do_fork
      test for 100 forks, you could use:
      	kgdbts=V1N6F100 kgdbwait
      
      The test suite can also be invoked at run time with:
      echo kgdbts=V1N6F100 > /sys/module/kgdbts/parameters/kgdbts
      Or as another example:
      echo kgdbts=V2 > /sys/module/kgdbts/parameters/kgdbts
      
      When developing a new kgdb arch specific implementation or
      using these tests for the purpose of regression testing,
      several invocations are required.
      
      1) Boot with the test suite enabled by using the kernel arguments
            "kgdbts=V1F100 kgdbwait"
         ## If kgdb arch specific implementation has NMI use
            "kgdbts=V1N6F100
      
      2) After the system boot run the basic test.
      echo kgdbts=V1 > /sys/module/kgdbts/parameters/kgdbts
      
      3) Run the concurrency tests.  It is best to use n+1
         while loops where n is the number of cpus you have
         in your system.  The example below uses only two
         loops.
      
      ## This tests break points on sys_open
      while [ 1 ] ; do find / > /dev/null 2>&1 ; done &
      while [ 1 ] ; do find / > /dev/null 2>&1 ; done &
      echo kgdbts=V1S10000 > /sys/module/kgdbts/parameters/kgdbts
      fg # and hit control-c
      fg # and hit control-c
      ## This tests break points on do_fork
      while [ 1 ] ; do date > /dev/null ; done &
      while [ 1 ] ; do date > /dev/null ; done &
      echo kgdbts=V1F1000 > /sys/module/kgdbts/parameters/kgdbts
      fg # and hit control-c
      Signed-off-by: NJason Wessel <jason.wessel@windriver.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      e8d31c20
  2. 09 2月, 2008 1 次提交
  3. 08 2月, 2008 1 次提交
  4. 06 2月, 2008 2 次提交
    • C
      tc1100-wmi: Add driver for HP Compaq TC1100 Tablets · dd8cd779
      Carlos Corbacho 提交于
      This is based on the 2004 out-of-tree work of Jamey Hicks, to add
      support via WMI for controlling the jog dial and wireless on these
      tablets.
      
      v1:
      
      Original release
      
      v2:
      
      As per Joshua Wise's comments, change bluetooth to jogdial (an error from
      the original driver).
      Signed-off-by: NCarlos Corbacho <carlos@strangeworlds.co.uk>
      CC: Matthew Garrett <mjg59@srcf.ucam.org>
      CC: Jamey Hicks <jamey.hicks@nokia.com>
      CC: Joshua Wise <joshua@joshuawise.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      dd8cd779
    • C
      acer-wmi: Add driver for newer Acer laptops · 745a5d21
      Carlos Corbacho 提交于
      This is a driver for newer Acer (and Wistron) laptops. It adds wireless
      radio and bluetooth control, and on some laptops, exposes the mail LED and
      LCD backlight.
      
      v1:
      
      * Initial release
      
      v2:
      
      * Replace left over ACPI references with WMI
      * Add GUID based autoloading (depends on future work to WMI)
      * Add DMI based autoloading (backup solution until WMI sysfs/ class
        work is available)
      * Checkpatch fixes
      
      v3:
      
      * Add new EC quirks for Aspire 3100 & 5100, and Extensa 5220
      
      v4:
      
      * Simplified internal handling of WMID and AMW0 devices
      * Add autodetection for bluetooth and maximum brightness on AMW0 V2 and
        WMID laptops.
      
      v5:
      
      * Add EC quirk for Medion MD 98000
      * Add autodetection for AMW0, and mail LED on AMW0 and AMW0 V2.
      * Improve error handling
      * Fix AMW0 V2 bluetooth and wireless, by using both WMID and AMW0 methods
        to ensure that the correct value is always set.
      
      v6:
      
      * Fix 'use before initialisation' bug with quirks.
      
      v7
      
      * Fix bug on AMW0 where acer-wmi would exit if a mail LED was not
        detected.
      * Add Acer Aspire 9110 mail LED support
      * Fix section mismatch warnings
      Signed-off-by: NCarlos Corbacho <carlos@strangeworlds.co.uk>
      CC: Matthew Garrett <mjg59@srcf.ucam.org>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      745a5d21
  5. 02 2月, 2008 1 次提交
  6. 17 10月, 2007 1 次提交
  7. 29 8月, 2007 1 次提交
  8. 09 7月, 2007 1 次提交
  9. 05 7月, 2007 1 次提交
    • L
      Remove the blink driver · 2bcb1b7d
      Linus Torvalds 提交于
      Yeah, we could have just disabled it, but there's work on a new one that
      isn't as fundamentally broken, so there really doesn't seem to be any
      point in keeping it around.
      
      The recent timer cleanup broke the only valid use, and when I say
      "valid", I obviously mean "totally broken".  So it's not like it works,
      or really even can work in the current format that uses the unsafe
      "panic" LED blinking routines..
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      2bcb1b7d
  10. 09 5月, 2007 2 次提交
  11. 31 3月, 2007 2 次提交
  12. 26 3月, 2007 1 次提交
  13. 13 2月, 2007 1 次提交
  14. 30 1月, 2007 1 次提交
  15. 17 10月, 2006 1 次提交
  16. 14 10月, 2006 1 次提交
  17. 04 10月, 2006 1 次提交
  18. 02 10月, 2006 1 次提交
    • A
      [PATCH] Linux Kernel Dump Test Module · 8bb31b9d
      Ankita Garg 提交于
      A simple module to test Linux Kernel Dump mechanism.  This module uses
      jprobes to install/activate pre-defined crash points.  At different crash
      points, various types of crashing scenarios are created like a BUG(),
      panic(), exception, recursive loop and stack overflow.  The user can
      activate a crash point with specific type by providing parameters at the
      time of module insertion.  Please see the file header for usage
      information.  The module is based on the Linux Kernel Dump Test Tool by
      Fernando <http://lkdtt.sourceforge.net>.
      
      This module could be merged with mainline. Jprobes is used here so that the
      context in which crash point is hit, could be maintained. This implements
      all the crash points as done by LKDTT except the one in the middle of
      tasklet_action().
      Signed-off-by: NAnkita Garg <ankita@in.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      8bb31b9d
  19. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4