-----Original Message-----
From: Corey Minyard <[email protected]> On Behalf Of Corey Minyard
Sent: Friday, April 12, 2019 5:12 PM
To: Asmaa Mnebhi <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v1 1/1] Support IPMB
>
> What is /dev/ipmb-dev, btw? I'm not familiar with that? Is it just a normal
> I2C channel on Linux?
>
> It is just normal smbus/i2c channel on Linux. I have a linux driver that
> works hand in hand with this OpenIPMI code. It creates the /dev/ipmb-dev
> device file so that OpenIPMI can use it. That is how I have been testing my
> code. I will post the linux ipmb driver shortly.
>
Is there any reason it needs to be a driver? For this application it would
seem better to me to make it part of the userland code.
-corey
It seems to me it is worth doing since any Satellite MC (running linux for
example) which is receiving an IPMB request from a BMC, would have an I2C
driver to receive that request. Linux I2C driver requires defining a callback
function to be able to register the device as an I2C slave. That callback
function just describes what to do when a READ/WRITE is requested. So in my
driver, I define the callback function (similar to what was done in
i2c-slave-eeprom.c), and I define read/write functions for userspace to
interact with the kernel. It is pretty handy since the requests are queued up
in the driver and sent to userspace (in this case, OpenIPMI) one at a time.
Thanks.
Asmaa
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer
