From: Andreas Oberritter <obi@saftware.de>
To: Robin Gilks <robin.gilks@tait.co.nz>
Cc: linuxppc-embedded@lists.linuxppc.org,
Tom Rini <trini@kernel.crashing.org>
Subject: Re: wdt_mpc8xx documentation
Date: Thu, 18 Dec 2003 06:52:46 +0100 [thread overview]
Message-ID: <1071726766.3533.11.camel@shiva.eth.saftware.de> (raw)
In-Reply-To: <3FE12DCD.10609@tait.co.nz>
Hi Robin,
Have a look at our driver, which uses the kernel's watchdog api:
http://cvs.tuxbox.org/cgi-bin/viewcvs.cgi/*checkout*/tuxbox/cdk/Patches/linux-2.4.23-pre6-m8xxwdt.diff?rev=HEAD&content-type=text/plain
It will probably never get into vanilla 2.4 because Marcelo doesn't
respond to my Emails. However, it is really stable since months...
What other driver were you talking about?
Tom, would you put this driver into the 2.4 ppc trees if I rediffed it?
Regards,
Andreas
On Thu, 2003-12-18 at 05:32, Robin Gilks wrote:
> Greetings
>
> Whilst rummaging about the PPC development tree I came across the
> Siemens/SGI/Denx watchdog driver for the mpc8xx. It references a man
> page which so far I've not been able to find (man wdt_mpx8xx(4)) so I'm
> a bit clueless about what the monitor chain code does.
>
> It doesn't seem to relate to the generic watchdog_api.txt in the kernel
> documentation (at least the defines don't seem to tie in with any of the
> ioctl options).
>
> Any help here appreciated.
>
> --
> Robin Gilks
> Senior Design Engineer Phone: (+64)(3) 357 1569
> Tait Electronics Fax : (+64)(3) 359 4632
> PO Box 1645 Christchurch Email : robin.gilks@tait.co.nz
> New Zealand
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-18 5:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 4:32 wdt_mpc8xx documentation Robin Gilks
2003-12-18 5:52 ` Andreas Oberritter [this message]
2003-12-18 16:13 ` Tom Rini
2003-12-18 16:59 ` Andreas Oberritter
2003-12-18 22:10 ` Robin Gilks
2003-12-19 20:30 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1071726766.3533.11.camel@shiva.eth.saftware.de \
--to=obi@saftware.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=robin.gilks@tait.co.nz \
--cc=trini@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).