This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

IPMI driver for KCS interface

From: jerzy dyrda <jerzy dot dyrda at kontron dot pl>
To: ecos-discuss at ecos dot sourceware dot org
Date: Wed, 11 Jul 2007 13:12:49 +0200
Subject: [ECOS] IPMI driver for KCS interface
References: <d5aafeec0707050733h67301df3w8bdbd670f529e8a1@mail.gmail.com> <003c01c7c30a$40480720$7101a8c0@Kimbara> <d5aafeec0707101125y325de419q82dc494974a78559@mail.gmail.com>

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

Follow-Ups:
- RE: IPMI driver for KCS interface
  - From: Laurie Gellatly
- Re: IPMI driver for KCS interface
  - From: Andrew Lunn

References:
- Re: eCos invalidating JTAG on ARM architecture ?
  - From: Alexandre
- Re: Re: eCos invalidating JTAG on ARM architecture ?
  - From: Andy Jackson
- Re: Re: eCos invalidating JTAG on ARM architecture ?
  - From: Alexandre

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]