An error occurred fetching the project authors.
  1. 15 Jan, 2006 1 commit
    • Calin A. Culianu's avatar
      [PATCH] Watchdog: Winsystems EPX-C3 SBC · eed6565f
      Calin A. Culianu authored
      This is a 2.6 patch that adds support for the watchdog timer built into the
      EPX-C3 single board computer manufactured by Winsystems, Inc.
      
      Driver details:
      
      This is for x86 only.  This watchdog is pretty basic and simple.  It is
      only configurable via jumpers on the SBC, and it only has either a 1.5s or
      200s interval.  The watchdog can either be auto-configured to start as soon
      as the machine powers up (bad idea for the 1.5s interval!) or it can be
      enabled and disabled by writing to io port 0x1ee.  Petting the watchdog
      involves writing any value to io port 0x1ef.
      
      The only unfortunate thing about this watchdog (and it is not at all
      uncommmon in watchdogs that linux supports) is that it is not a PCI or
      ISA-PNP device and as such it isn't at all probeable.  Either the watchdog
      exists as 2 bytes at 0x1ee, or it doesn't.  Thus, using this driver on a
      machine that doesn't have that watchdog can potentially hang/crash the
      system, etc.  So only use this driver if you in fact are on a Winsystems
      EPX-C3 SBC.
      
      Anyway this driver fits into the already-existing watchdog framework quite
      nicely and I already tested it on my EPX-C3 and it works like a charm.
      Signed-off-by: default avatarCalin A. Culianu <calin@ajvar.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      eed6565f
  2. 12 Sep, 2005 2 commits
  3. 11 Sep, 2005 3 commits
  4. 10 Sep, 2005 2 commits
  5. 05 Sep, 2005 1 commit
    • Kumar Gala's avatar
      [PATCH] ppc32: Added support for the Book-E style Watchdog Timer · a2f40ccd
      Kumar Gala authored
      PowerPC 40x and Book-E processors support a watchdog timer at the processor
      core level.  The timer has implementation dependent timeout frequencies
      that can be configured by software.
      
      One the first Watchdog timeout we get a critical exception.  It is left to
      board specific code to determine what should happen at this point.  If
      nothing is done and another timeout period expires the processor may
      attempt to reset the machine.
      
      Command line parameters:
        wdt=0 : disable watchdog (default)
        wdt=1 : enable watchdog
      
        wdt_period=N : N sets the value of the Watchdog Timer Period.
      
        The Watchdog Timer Period meaning is implementation specific. Check
        User Manual for the processor for more details.
      
      This patch is based off of work done by Takeharu Kato.
      Signed-off-by: default avatarMatt McClintock <msm@freescale.com>
      Signed-off-by: default avatarKumar Gala <kumar.gala@freescale.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      a2f40ccd
  6. 03 Sep, 2005 2 commits
  7. 22 Jun, 2005 1 commit
    • Utz Bacher's avatar
      [PATCH] ppc64: add a watchdog driver for rtas · 031f7ede
      Utz Bacher authored
      Add a watchdog using the RTAS OS surveillance service. This is
      provided as a simpler alternative to rtasd. The added value
      is that it works with standard watchdog client programs and
      can therefore also do user space monitoring.
      
      On BPA, rtasd is not really useful because the hardware does
      not have much to report with event-scan.
      
      The driver should also work on other platforms that support
      the OS surveillance rtas calls.
      Signed-off-by: default avatarArnd Bergmann <arndb@de.ibm.com>
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      031f7ede
  8. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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