Re: [Openhpi-devel] How to add FRU resource at the RPT

[Renier M. <re...@us...>]

ope...@li... wrote on 06/03/2008 10:09:48 
AM:

> Hi All,
> I got an HPI implementation question.
> When a FRU inserted in the system it is not allowed to use “Resource
> Added” event and after FRU was extracted the resource should removed.
>  “However, the “Resource Added” event described in Section 3.8.1 on 
> page 26 should never be used for a FRU resource. If a FRU resource 
> is added to an RPT after HPI initialization, this should always be 
> reported as a hot swap event, as described in Section 7.7 on page 132”
> “When a FRU entity is inserted into or removed from the system, the 
> corresponding resource is added to or removed from all domains in 
> which that resource is visible, and the RPTs in those domains are 
> updated accordingly.”
> When FRU inserted its resource does not exist yet (at the RPT). How 
> the HW \ HPI-implementation can send a FRU\Hot Swap change state 
> event since this event regards to specific resource and this one 
> does not exist yet?
> The FRU\Hot Swap event contains only state changes (previous and 
> current state) and does not contain the new resource information. In
> this point since the “Resource Added” event is forbidden the only 
> way to add the new resource is applying Discover function and this 
> can be long operation. Is it correct?

For new FRU and Non-FRU resources, plugins send an oh_event struct to the 
infrastructure (see oh_event.h in source code).
This structure contains the SaHpiEventT (where you would put the hotswap 
event information), the resource information (SaHpiRptEntryT), and a 
linked list of the RDRs for that resource. For subsequent events regarding 
that same resource, only the SaHpiEventT needs to be set within the 
oh_event structure.

        --Renier