1. 23 11月, 2007 1 次提交
  2. 15 11月, 2007 5 次提交
  3. 07 11月, 2007 2 次提交
  4. 06 11月, 2007 2 次提交
  5. 01 11月, 2007 1 次提交
  6. 30 10月, 2007 1 次提交
  7. 29 10月, 2007 1 次提交
  8. 26 10月, 2007 1 次提交
  9. 23 10月, 2007 1 次提交
  10. 21 10月, 2007 1 次提交
  11. 20 10月, 2007 4 次提交
  12. 19 10月, 2007 1 次提交
    • A
      serial: turn serial console suspend a boot rather than compile time option · 8f4ce8c3
      Andres Salomon 提交于
      Currently, there's a CONFIG_DISABLE_CONSOLE_SUSPEND that allows one to stop
      the serial console from being suspended when the rest of the machine goes
      to sleep.  This is incredibly useful for debugging power management-related
      things; however, having it as a compile-time option has proved to be
      incredibly inconvenient for us (OLPC).  There are plenty of times that we
      want serial console to not suspend, but for the most part we'd like serial
      console to be suspended.
      
      This drops CONFIG_DISABLE_CONSOLE_SUSPEND, and replaces it with a kernel
      boot parameter (no_console_suspend).  By default, the serial console will
      be suspended along with the rest of the system; by passing
      'no_console_suspend' to the kernel during boot, serial console will remain
      alive during suspend.
      
      For now, this is pretty serial console specific; further fixes could be
      applied to make this work for things like netconsole.
      Signed-off-by: NAndres Salomon <dilinger@debian.org>
      Acked-by: N"Rafael J. Wysocki" <rjw@sisk.pl>
      Acked-by: NPavel Machek <pavel@ucw.cz>
      Cc: Nigel Cunningham <nigel@suspend2.net>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      8f4ce8c3
  13. 17 10月, 2007 9 次提交
  14. 16 10月, 2007 1 次提交
  15. 14 10月, 2007 1 次提交
  16. 13 10月, 2007 2 次提交
  17. 08 10月, 2007 1 次提交
  18. 05 10月, 2007 1 次提交
    • S
      [POWERPC] cpm: Describe multi-user ram in its own device node. · 15f8c604
      Scott Wood 提交于
      The way the current CPM binding describes available multi-user (a.k.a.
      dual-ported) RAM doesn't work well when there are multiple free regions,
      and it doesn't work at all if the region doesn't begin at the start of
      the muram area (as the hardware needs to be programmed with offsets into
      this area).  The latter situation can happen with SMC UARTs on CPM2, as its
      parameter RAM is relocatable, u-boot puts it at zero, and the kernel doesn't
      support moving it.
      
      It is now described with a muram node, similar to QE.  The current CPM
      binding is sufficiently recent (i.e. never appeared in an official release)
      that compatibility with existing device trees is not an issue.
      
      The code supporting the new binding is shared between cpm1 and cpm2, rather
      than remain separated.  QE should be able to use this code as well, once
      minor fixes are made to its device trees.
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      15f8c604
  19. 04 10月, 2007 3 次提交
  20. 03 10月, 2007 1 次提交