From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32637 invoked by alias); 12 Jul 2007 07:16:23 -0000 Received: (qmail 32627 invoked by uid 22791); 12 Jul 2007 07:16:21 -0000 X-Spam-Check-By: sourceware.org Received: from mail2.trafficmaster.net (HELO mail2.trafficmaster.co.uk) (83.100.242.16) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 12 Jul 2007 07:16:18 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 12 Jul 2007 07:16:00 -0000 Message-ID: In-Reply-To: <200707111433.40133.jerzy.dyrda@kontron.pl> References: <200707111433.40133.jerzy.dyrda@kontron.pl> From: "David Fernandez" To: "jerzy dyrda" , Cc: "Laurie Gellatly" Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] IPMI driver for KCS interface X-SW-Source: 2007-07/txt/msg00108.txt.bz2 > -----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 >=20 > Hello Laurie, >=20 > > 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? >=20 > 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. >=20 > 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 =20 ----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