From 044f03861f863ad8a602d943d5a2ba77c1062a88 Mon Sep 17 00:00:00 2001 From: Joachim Fenkes Date: Thu, 16 May 2019 15:57:31 +0200 Subject: FAPI2: Clarify that broadcast groups must be mapped explicitly Change-Id: I7401b265eb3a5166eadacda14b4c1b58bfc7c908 Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/77457 Tested-by: FSP CI Jenkins Tested-by: Jenkins Server Tested-by: PPE CI Tested-by: Hostboot CI Tested-by: HWSV CI Reviewed-by: Joseph J. McGill Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/77463 Reviewed-by: RAJA DAS --- src/import/hwpf/fapi2/include/fapi2_hw_access.H | 3 +++ 1 file changed, 3 insertions(+) (limited to 'src/import/hwpf') diff --git a/src/import/hwpf/fapi2/include/fapi2_hw_access.H b/src/import/hwpf/fapi2/include/fapi2_hw_access.H index f824d30b..76d186a9 100644 --- a/src/import/hwpf/fapi2/include/fapi2_hw_access.H +++ b/src/import/hwpf/fapi2/include/fapi2_hw_access.H @@ -91,6 +91,9 @@ inline OpModes getOpMode(void); /// result in error. /// i_mappings may contain an arbitrary amount of abstract/HW pairs, but the /// function may return an error if too many mappings are specified. +/// If the hardware supports a "broadcast" group, that must also be mapped +/// explicitly via this function - platforms are not expected to map the +/// broadcast group implicitly. template< MulticastType M, typename V > inline ReturnCode setMulticastGroupMap(const Target& i_chip, const std::vector< MulticastGroupMapping >& i_mappings); -- cgit v1.2.1