Hey Andrew,

> Perhaps adding a parameter to the functions, a field to the template, 
> etc.

Sorry, I may have stated it incorrectly.  The issue I see is that there
is no field in the KCS header for the slave address.  That's why I'm not
quite sure if the KCS interface can even contact something other than
the BMC.  You can see the header in section 9.1 of the specification.

> Does this need a bugzilla to track it?  

Nah, its on our list in CVS (see TODO).  Of course, when we get around
to this is a different story.  I hope to get some IPMI development time
in a month or so.

Al

--
Albert Chu
[EMAIL PROTECTED]
Lawrence Livermore National Laboratory

----- Original Message -----
From: "Cress, Andrew R" <[EMAIL PROTECTED]>
Date: Wednesday, May 25, 2005 11:31 am
Subject: RE: [Freeipmi-devel] Need to issue commands to non-BMC slave
addresses

> Al,
> 
> Thanks for the tip about fidd_obj_set().
> 
> The IPMI FRU commands to the HSC are still SMS messages, just the 
> targethas a different slave address.  (See IPMI 2.0 section 5, pg 37,
> "Requester's ID") This problem becomes decidedly more acute with 
> bladedsystems.  So, there needs to be a method for both local (KCS 
> or SSIF)
> and remote (LAN or Serial) addressing to cover it.  Perhaps adding a
> parameter to the functions, a field to the template, etc.
> 
> Does this need a bugzilla to track it?  
> 
> Andy 
> 
> -----Original Message-----
> From: Albert Chu [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, May 25, 2005 12:12 PM
> To: Cress, Andrew R
> Cc: GNU FreeIPMI Developers
> Subject: Re: [Freeipmi-devel] Need to issue commands to non-BMC slave
> addresses
> 
> Hey Andrew,
> 
> > Comments/advice?
> 
> For lan, in the short term, I think the best thing to do is to use the
> fiid_obj_set() function to manually set the field "rs_addr" of the
> tmpl_lan_msg_hdr_rq template.  I'm not quite sure what to for KCS
> though.  As far as I can tell, it can only go to the BMC and nothing
> else.  According to the IPMI 2.0 spec, beginning of Chapter 9.
> 
> "The KCS interface is specified solely for SMS messages"
> 
> indicating it can't be done??  AB, your thoughts?
> 
> For the long term though, I believe this has to be fixed in the
> libfreeipmi library API somehow.  We simply assume all transactions go
> to the BMC slave address, but its apparently not a correct assumption.
> I'll add it to the todo list.
> 
> Al
> 
> --
> Albert Chu
> [EMAIL PROTECTED]
> Lawrence Livermore National Laboratory
> 
> ----- Original Message -----
> From: "Cress, Andrew R" <[EMAIL PROTECTED]>
> Date: Wednesday, May 25, 2005 8:50 am
> Subject: [Freeipmi-devel] Need to issue commands to non-BMC slave
> addresses
> 
> > 
> > In my utilities, there are a few cases where IPMI commands (for FRU)
> > need to be sent to a slave address other than the BMC slave address
> > (0x20).  For instance, in our platforms the HotSwap Controller 
> has 
> > IPMIFRU data at slave address 0xC0.  
> > I currently have no way of passing a different slave address to
> > ipmi_kcs_cmd_interruptible() or  ipmi_lan_cmd().
> > 
> > I noticed that fill_lan_msg_hdr() inserts a constant BMC slave 
> > address,but I didn't find where the kcs template had a place for 
> > the slave
> > address.
> > 
> > Comments/advice?
> > 
> > Andy
> > 
> > 
> > 
> > _______________________________________________
> > Freeipmi-devel mailing list
> > Freeipmi-devel@gnu.org
> > http://lists.gnu.org/mailman/listinfo/freeipmi-devel
> > 
> 
> 



_______________________________________________
Freeipmi-devel mailing list
Freeipmi-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/freeipmi-devel

Reply via email to