On Mon, 2014-11-10 at 17:01 +1100, Alistair Popple wrote: > Ben, > > > > > Our OPAL interface can only do one at a time ? Because our underlying FW > > driver already has a queue .. > > The OPAL interface supports sending more than one message at a time using the > underlying FW queue as you suggest. However in theory the interface doesn't > make any response order guarantees, but in practice they should be ordered as > our BMC doesn't send out-of-order responses.
Can't we put some ID in the response message ? OPAL messages have room... Cheers, Ben. > Regards, > > Alistair > > > > > I'll look at doing that. If that is the case, then your NULL check > > > > for current message should probably be a BUG_ON(). > > > > > > OK, I'll update this when the msghandler bit is implemented. > > > > > > > Do you need to handle any BMC flags? Particularly incoming events? > > > > > > Not at this stage - we may in future though. > > > > > > Cheers, > > > > > > > > > Jeremy > > > _______________________________________________ > > > Linuxppc-dev mailing list > > > Linuxppc-dev@lists.ozlabs.org > > > https://lists.ozlabs.org/listinfo/linuxppc-dev > > > > _______________________________________________ > > Linuxppc-dev mailing list > > Linuxppc-dev@lists.ozlabs.org > > https://lists.ozlabs.org/listinfo/linuxppc-dev _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev