Thanks for the reply Corey. The board is actually not a Katana, although I used the Katana device tree stuff as reference for porting 2.6.24 to this board. This board is a One Stop Systems (formerly SBE) board that we are using as a PTMC carrier for some daughter boards that we need to use. From the hardware centric Zircon docs that I have, it 'looks like' the device supports both KCS and BT standard interfaces.
Unfortunately, this Zircon device has been EOL'ed by QLogic, and I have been unable to get any additional documentation beyond what I already have. So, I'm pretty clueless on what the driver configuration parameters should be. I'm hoping someone else reading this will have a copy of the needed Zircon docs that they could send to me. In any case, I'll keep working on it. I appreciate the info. Happy holidays! Stephen -----Original Message----- From: Corey Minyard [mailto:[email protected]] Sent: Friday, December 19, 2008 4:51 PM To: Stephen Horton Cc: [email protected] Subject: Re: [Openipmi-developer] Zircon PM connected to Marvell SystemController and MPC7448 I don't think ipmi_si will work, that's the driver for the standard system interfaces. I'm guessing it's a Katana. If so, your board connects to the PM over the I2C bus, and it does not use the IPMI-specified interface over I2C (because that didn't exist when the board was designed). If that's the case, a driver does exist for this board, but it doesn't tie into the standard IPMI interface and I don't have a copy of it. If it's not a Katana, it is possible that the PM had a standard SI interface, if so you just need the interface type, address, address spacing, interrupt, etc. Your best bet is to try to get the info from the manufacturer. It's not a huge deal that this is a PM vs a BMC, the only problem will be that the driver will assume that the local MCs IPMB address is 0x20 unless you override that. -corey Stephen Horton wrote: > > Howdy OpenIPMI developers, > > I'm a newbie to doing this the hard way, so please forgive me. I have > recently inherited an older CompactPCI board that has a Zircon PM > (peripheral management controller that supports IPMI 1.0). Previous > developers of this board did not do the work to get IPMI working, but > I need to. > > The board has a Marvell System Controller (MV64462) and Freescale > Powerpc MPC7448, and I have upgraded the board to run Powerpc Linux > 2.6.24 using a device tree to control configuration (so > CONFIG_PPC_OF=y). On this board, the Marv > > the sample script is simply blows up with "open failed" and no hint why > > ell I2c port is connected to port 1 (IPMB enabled port) of the > ZirconPM device. There is a CPLD controlled switch that allows me to > connect the Marvell I2c port to the SPD of the SDRAM Memory and read > the DIMM specific information; thus, I know the Marvell I2c port is > configured and working properly. Also, a member of my team was able to > get FRU programmed into the device using a special I2c to USB adapter > cable and writing the raw FRU to the device. And, I verified that both > FRU and GetDeviceID can be read from my chassis management module over > the CompactPCI midplane (so I know the device is at least somewhat > working). > > Now, I am unable to get the ipmi_si driver to load. I am getting the > following error (with some additional logs added by me): > > bus platform: add driver ipmi > > ipmi message handler version 39.1 > > bus platform: add driver ipmi_si > > IPMI System Interface driver. > > __pci_register_driver: driver name is ipmi_si > > bus pci: add driver ipmi_si > > bus of_platform: add driver ipmi > > bus pci: remove driver ipmi_si > > bus of_platform: remove driver ipmi > > bus platform: remove driver ipmi_si > > ipmi_si: Unable to find any System Interface(s) > > bus platform: remove driver ipmi > > Closer inspection shows me that when the platform bus is probed, there > is no match found for the device / driver. Below is the swag I took at > adding a device tree node for this: > > ipmi { > > device_type = "ipmi"; > > compatible = "ipmi-kcs"; > > reg = <0xca8 8>; > > /* ports = <0xca2>; */ > > reg-spacing = <4>; > > reg-size = <1>; > > reg-shift = <0>; > > }; > > Does anyone have any experience and tips interfacing a Zircon with a > Marvell controller? Do I need to have concerns about this device being > a PM and not a BMC? Can anyone offer a device tree snippet to help me? > I really don't know what I'm doing here. I have a number of Zircon > hardware centric reference documents, but very little software > guidance on this. Corey, I have read your IPMI.txt file, and your > Gentle Guide to IPMI, but forgive me for being slow. > > Regards, > > Stephen Horton > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------ ------ > > ------------------------------------------------------------------------ > > _______________________________________________ > Openipmi-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openipmi-developer > ------------------------------------------------------------------------------ _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
