From: "David Härdeman" <david@2gen.com>
To: Bukie Mabayoje <bukiemab@gte.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IPMI smbus and Intel 6300ESB Watchdog drivers
Date: Mon, 31 Jan 2005 21:52:35 +0100 [thread overview]
Message-ID: <20050131205234.GC26992@hardeman.nu> (raw)
In-Reply-To: <41FD5EFB.D6E39F5E@gte.net>
On Sun, Jan 30, 2005 at 02:26:03PM -0800, Bukie Mabayoje wrote:
>David Härdeman wrote:
>> 1) On the mainboard is a 6300ESB Watchdog Timer (pci id 8086:25ab), but
>> there seems to be no driver available for it.
>
>6300ESB is not a Watchdog Timer. It is an I/O Controller hub that includes a watch dog timer.
Ah well, I just quoted the output of lspci...
>> Does anyone know if there
>> is any such driver in progress or if I've misunderstood the situation?
>
>If you tell me why you are interested in the WDT, then maybe I will be able answer your question.
Hummm? In order to have watchdog functionality on the machine? But
nevermind, I already got that question answered (with the pci id update
for i8xx_tco).
>>
>>
>> 2) IPMI, Documentation/IPMI.txt mentions a ipmi_smb driver, but I could
>> find no such driver in the 2.6.10 tree. Am I missing something?
>
>Do you get the ISM package that shipped with the board? The ISM software stack in not part of the kernel. The IPMI stuff is part of Server Management.
>
As for IPMI, I have no idea, I just have no experience of it at all and
I saw that this mmotherboard supported IPMI so I thought it could be an
interesting experiment to learn a bit more about IPMI.
Re,
David
prev parent reply other threads:[~2005-01-31 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 18:44 IPMI smbus and Intel 6300ESB Watchdog drivers David Härdeman
2005-01-30 21:13 ` Peter Lundkvist
2005-01-31 20:46 ` David Härdeman
2005-01-30 22:26 ` Bukie Mabayoje
2005-01-31 20:52 ` David Härdeman [this message]
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=20050131205234.GC26992@hardeman.nu \
--to=david@2gen.com \
--cc=bukiemab@gte.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.