From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: wim@iguana.be, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] watchdog: Add watchdog timer support for the WinSystems EBC-C384
Date: Tue, 26 Jan 2016 18:38:57 -0500 [thread overview]
Message-ID: <56A80391.40009@gmail.com> (raw)
In-Reply-To: <56A6CB48.4010402@roeck-us.net>
On 01/25/2016 08:26 PM, Guenter Roeck wrote:
>> The manual for this motherboard does not provide much information about
>> the Super I/O chip (no model number, etc.), and neither sensors-detect
>> nor superiotool was able to detect it. I've sent an email to the
>> motherboard company (WinSystems) requesting further information about
>> the Super I/O chip and whether the watchdog timer is built-in to the
>> Super I/O chip.
>>
>
> Ah, I somehow thought you were associated with WinSystems, since you know
> how to configure the chip.
>
> Did you get any useful output from sensors-detect or superiotool
> (like 'unknown chip xxxx'), or did those tools find nothing ?
Unfortunately, the sensors-detect only reported "No" for each Super I/O
chip test, while the superiotool gave an unhelpful "No Super I/O chip
detected" message.
I haven't heard a response yet from WinSystems, but I'll give them a
couple days before sending another email to their engineering
department. For now, I'll submit a version 4 of this patch to get the
minor updates I made out for review; for what its worth, I believe the
dmi_match method will be sufficient until I get an update from
WinSystems helping me get a proper check to identify the Super I/O chip.
William Breathitt Gray
next prev parent reply other threads:[~2016-01-26 23:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 19:09 [PATCH v3] watchdog: Add watchdog timer support for the WinSystems EBC-C384 William Breathitt Gray
2016-01-25 19:28 ` One Thousand Gnomes
2016-01-25 20:42 ` Guenter Roeck
2016-01-25 23:36 ` William Breathitt Gray
2016-01-26 1:26 ` Guenter Roeck
2016-01-26 23:38 ` William Breathitt Gray [this message]
2016-01-27 5:02 ` Guenter Roeck
2016-01-28 0:18 ` William Breathitt Gray
2016-01-28 1:51 ` Guenter Roeck
2016-01-28 11:05 ` One Thousand Gnomes
2016-01-26 1:58 ` Guenter Roeck
2016-02-28 14:07 ` Wim Van Sebroeck
2016-02-28 14:36 ` William Breathitt Gray
2016-02-28 15:02 ` Guenter Roeck
2016-02-28 16:24 ` Wim Van Sebroeck
2016-01-26 1:11 ` Guenter Roeck
2016-01-26 9:09 ` Paul Bolle
2016-01-26 12:33 ` William Breathitt Gray
-- strict thread matches above, loose matches on Subject: below --
2016-01-26 14:31 William Breathitt Gray
2016-01-26 15:30 ` Guenter Roeck
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=56A80391.40009@gmail.com \
--to=vilhelm.gray@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@iguana.be \
/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).