RE: [ECOS] IPMI driver for KCS interface

["David Fernandez" <david.fernandez@trafficmaster.co.uk>]

> -----Original Message-----
> From: jerzy dyrda [mailto:jerzy.dyrda@kontron.pl]
> Sent: 11 July 2007 13:34
> To: ecos-discuss@ecos.sourceware.org
> Cc: Laurie Gellatly
> Subject: Re: [ECOS] IPMI driver for KCS interface
> 
> Hello Laurie,
> 
> > 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?
> 
> Yes, IPMI as I suppose is in general method of comunication with
Baseboard
> Management Controller - BMC ( from side of System Management Software
-
> SMS )
> but KCS is kind of interface beetwen BMC and SMS (sorry for this
stupid
> shortcut but this is a part of IPMI terminology) and my doubts are
> connected
> with method of comunication from user application to BMD through KCS
> driver.
> IPMI specification defined other interfaces what force on developer
> implementing universal interface to IPMI.
> 
> Best regards,
> jezry

Hi there,

I've ported the Linux IPMI driver to Solaris some time ago.

I think you can just base your IPMI driver in the I2C driver if you were
going to use SMIC interface, I'm not so familiar with KCS, as it is very
slow interface and because of that is normally discarded in most
systems, in addition, most Intel chipsets have a BMC based on the SMIC
interface anyway.

Anyway, it is not very difficult to do the driver from scratch by just
looking at the standard if you intent to support just one interface and
don't have any intentions of offering very differentiated kernel and
user mode APIs.

Regards

 Trafficmaster, Plc.
David Fernandez
Wireless Comms. Specialist
 

----V-V-V-V----DISCARD-THE-FOLLOWING-DISCLAIMER----V-V-V-V----



--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss