1. 25 4月, 2014 1 次提交
  2. 17 4月, 2014 1 次提交
  3. 14 2月, 2014 3 次提交
  4. 07 2月, 2014 1 次提交
  5. 09 1月, 2014 1 次提交
  6. 08 1月, 2014 1 次提交
  7. 20 12月, 2013 1 次提交
  8. 30 10月, 2013 1 次提交
  9. 27 9月, 2013 1 次提交
  10. 13 9月, 2013 1 次提交
  11. 04 9月, 2013 1 次提交
  12. 31 8月, 2013 1 次提交
  13. 29 8月, 2013 1 次提交
  14. 27 7月, 2013 5 次提交
  15. 25 7月, 2013 1 次提交
  16. 20 6月, 2013 1 次提交
  17. 09 6月, 2013 1 次提交
  18. 07 6月, 2013 3 次提交
  19. 12 3月, 2013 2 次提交
  20. 09 2月, 2013 1 次提交
  21. 01 2月, 2013 1 次提交
  22. 19 1月, 2013 1 次提交
    • J
      tty: Added a CONFIG_TTY option to allow removal of TTY · 4f73bc4d
      Joe Millenbach 提交于
      The option allows you to remove TTY and compile without errors. This
      saves space on systems that won't support TTY interfaces anyway.
      bloat-o-meter output is below.
      
      The bulk of this patch consists of Kconfig changes adding "depends on
      TTY" to various serial devices and similar drivers that require the TTY
      layer.  Ideally, these dependencies would occur on a common intermediate
      symbol such as SERIO, but most drivers "select SERIO" rather than
      "depends on SERIO", and "select" does not respect dependencies.
      
      bloat-o-meter output comparing our previous minimal to new minimal by
      removing TTY.  The list is filtered to not show removed entries with awk
      '$3 != "-"' as the list was very long.
      
      add/remove: 0/226 grow/shrink: 2/14 up/down: 6/-35356 (-35350)
      function                                     old     new   delta
      chr_dev_init                                 166     170      +4
      allow_signal                                  80      82      +2
      static.__warned                              143     142      -1
      disallow_signal                               63      62      -1
      __set_special_pids                            95      94      -1
      unregister_console                           126     121      -5
      start_kernel                                 546     541      -5
      register_console                             593     588      -5
      copy_from_user                                45      40      -5
      sys_setsid                                   128     120      -8
      sys_vhangup                                   32      19     -13
      do_exit                                     1543    1526     -17
      bitmap_zero                                   60      40     -20
      arch_local_irq_save                          137     117     -20
      release_task                                 674     652     -22
      static.spin_unlock_irqrestore                308     260     -48
      Signed-off-by: NJoe Millenbach <jmillenbach@gmail.com>
      Reviewed-by: NJamey Sharp <jamey@minilop.net>
      Reviewed-by: NJosh Triplett <josh@joshtriplett.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      4f73bc4d
  23. 18 1月, 2013 1 次提交
  24. 16 1月, 2013 1 次提交
  25. 16 11月, 2012 2 次提交
  26. 31 10月, 2012 1 次提交
  27. 06 10月, 2012 1 次提交
  28. 27 9月, 2012 1 次提交
    • A
      tty/serial: Add kgdb_nmi driver · 0c57dfcc
      Anton Vorontsov 提交于
      This special driver makes it possible to temporary use NMI debugger port
      as a normal console by issuing 'nmi_console' command (assuming that the
      port is attached to KGDB).
      
      Unlike KDB's disable_nmi command, with this driver you are always able
      to go back to the debugger using KGDB escape sequence ($3#33).  This is
      because this console driver processes the input in NMI context, and thus
      is able to intercept the magic sequence.
      
      Note that since the console interprets input and uses polling
      communication methods, for things like PPP it is still better to fully
      detach debugger port from the KGDB NMI (i.e. disable_nmi), and use raw
      console.
      
      Usually, to enter the debugger one have to type the magic sequence, so
      initially the kernel will print the following prompt on the NMI debugger
      console:
      
      	Type $3#33 to enter the debugger>
      
      For convenience, there is a kgdb_fiq.knock kernel command line option,
      when set to 0, this turns the special command to just a return key
      press, so the kernel will be printing this:
      
      	Hit <return> to enter the debugger>
      
      This is more convenient for long debugging sessions, although it makes
      nmi_console feature somewhat useless.
      
      And for the cases when NMI connected to a dedicated button, the knocking
      can be disabled altogether by setting kgdb_fiq.knock to -1.
      Suggested-by: NColin Cross <ccross@android.com>
      Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      Acked-by: NAlan Cox <alan@linux.intel.com>
      Acked-by: NJason Wessel <jason.wessel@windriver.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      0c57dfcc
  29. 19 9月, 2012 1 次提交
  30. 18 9月, 2012 1 次提交