This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: IPMI driver for KCS interface
- From: "Laurie Gellatly" <laurie dot gellatly at netic dot com>
- To: "jerzy dyrda" <jerzy dot dyrda at kontron dot pl>, <ecos-discuss at ecos dot sourceware dot org>
- Date: Wed, 11 Jul 2007 21:38:32 +1000
- Subject: RE: [ECOS] IPMI driver for KCS interface
Hi Jerzy,
I've also got some interest in IPMI.
The way I expected it would be handled is as a set of library routines that
could be layered on top of a hardware transport layer (serial or IP for
instance).
I'm not an IPMI expert, but it appears to me that IPMI is basically a
communications protocol rather than a hardware driver.
Is that how you view it?
Cheers ...Laurie:{)
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org]On Behalf Of jerzy dyrda
Sent: Wednesday, 11 July 2007 9:13 PM
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] IPMI driver for KCS interface
Hello Folks,
My current task is create (maybe port from Linux) IPMI KCS driver for eCos.
I
have as always few doubts regarding new driver i.e. :
How should I construct driver whether it can be "authentic" eCos driver? (I
mean how this device should be accessible from user application side -
"direct" by special function or by io function e.g. read/write )
If someone from eCos comunity has some advice/tip/demand regarding IPMI it
will be very helpful and of course appreciate.
thanks,
jerzy
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss