On 09/06/2017 04:56 AM, Brendan Higgins wrote:
On Thu, Aug 24, 2017 at 6:01 AM, Corey Minyard wrote:
If you just need the ability to catch a few commands in the kernel, what you
have is fairly complicated. I think a simple notifier called from every
driver
would provide what you needed with j
On Thu, Aug 24, 2017 at 6:01 AM, Corey Minyard wrote:
> On 08/23/2017 01:03 AM, Brendan Higgins wrote:
>
>
>>
>> ...
As far as this being a complete design; I do not consider what I have
presented as being complete. I mentioned some things above that I would
like
to add a
On 08/23/2017 01:03 AM, Brendan Higgins wrote:
...
As far as this being a complete design; I do not consider what I have
presented as being complete. I mentioned some things above that I would
like
to add and some people have already chimed in asking for some changes.
I just wanted to get some
Sorry for the delayed response.
>>> This piece of code takes a communication interface, called a bus, and
>>> muxes/demuxes
>>> messages on that bus to various users, called devices. The name
>>> "devices"
>>> confused
>>> me for a bit, because I was thinking they were physical devices, what
>>>
I'm removing LKML because we are leaving the realm of kernel stuff and
talking mostly
about IPMI.
On 08/10/2017 08:06 PM, Brendan Higgins wrote:
On Thu, Aug 10, 2017 at 6:58 AM, Corey Minyard wrote:
On 08/07/2017 10:52 PM, Brendan Higgins wrote:
From: Benjamin Fair
This patch introduces a
On Thu, Aug 10, 2017 at 6:58 AM, Corey Minyard wrote:
> On 08/07/2017 10:52 PM, Brendan Higgins wrote:
>>
>> From: Benjamin Fair
>>
>> This patch introduces a framework for writing IPMI drivers which run on
>> a Board Management Controller. It is similar in function to OpenIPMI.
>> The framework
On 08/07/2017 10:52 PM, Brendan Higgins wrote:
From: Benjamin Fair
This patch introduces a framework for writing IPMI drivers which run on
a Board Management Controller. It is similar in function to OpenIPMI.
The framework handles registering devices and routing messages.
Ok, I think I unders
