From: "Chris Friesen" <cfriesen@nortel.com>
To: linux-kernel@vger.kernel.org, wim@iguana.be, chandra.konduru@intel.com
Subject: iTCO watchdog timer broken for Intel 3100 chipset
Date: Wed, 28 May 2008 11:17:38 -0600 [thread overview]
Message-ID: <483D93B2.9070809@nortel.com> (raw)
Hi all,
We've got a board with the Intel 3100 chipset. It shows a PCI id of
2670, which matches PCI_DEVICE_ID_INTEL_ESB2_0 and so the iTCO_wdt.c
driver happily initializes. However, the documentation for the TCO wdt
for this chipset doesn't match the implementation in the driver, so
things get messed up.
I'm not sure why the PCI IDs match, but maybe there is something else
that the iTCO_wdt driver should key off of to make sure it doesn't try
to run invalid code?
On another note, it appears that Intel has driver code (written for
2.6.18, under dual BSD/GPLv2) for the wdt for this chipset available at:
http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=2568&DwnldID=13653&lang=eng
Are there any plans to incorporate this into mainline?
Thanks,
Chris
reply other threads:[~2008-05-28 17:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=483D93B2.9070809@nortel.com \
--to=cfriesen@nortel.com \
--cc=chandra.konduru@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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