[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-devel] KCS Driver & SMS_ATN Register

From: Al Chu
Subject: Re: [Freeipmi-devel] KCS Driver & SMS_ATN Register
Date: Mon, 22 Feb 2010 07:17:04 -0800

Hey A.B.,

On Mon, 2010-02-22 at 01:16 -0800, Anand Babu Periasamy wrote:
> On Sun, Feb 21, 2010 at 8:38 AM, Al Chu <address@hidden> wrote:
> > Hey A.B,
> >
> >> Al, Unfortunately SMS_ATN is KCS specific. So we can't create an
> >> abstracted API.
> >
> > There's no reason other drivers won't have "interrupt callbacks" in the
> > future.  We can abstract it by calling the API function something like
> > "interrupt_callback".  The only driver supported with it would be KCS in
> > the beginning.
> >
> > Al
> Then lets create an API and return ENOTSUP erno for system interfaces
> other than KCS (for now). It makes sense for higher level abstracted
> API to call get-message-flags in addition. This function is already
> asynchronous.  Application developers would prefer an async API over
> callback framework.

We'd probably return IPMI_ERR_DEVICE_NOT_SUPPORTED  or make a new error
code, but yeah, that's the basic idea.


> --
> Anand Babu Periasamy
> GPG Key ID: 0x62E15A31
> Blog [http://*www.*]
> GlusterFS [http://*www.*]
> GNU Operating System [http://*www.*]
Albert Chu
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory

reply via email to

[Prev in Thread] Current Thread [Next in Thread]