PEL: Move definitions and variables to the proper scope
Some of the variables and definitions defined in the header
file are used only in the implementation file, so moving those
to the implementation file itself.
Tested:
No testing is required only need to pass compilation.
Change-Id: I4db72c12185b81c4e3e6dfa3f26d69081453c753
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
diff --git a/extensions/openpower-pels/sbe_ffdc_handler.cpp b/extensions/openpower-pels/sbe_ffdc_handler.cpp
index 183db37..d1a2469 100644
--- a/extensions/openpower-pels/sbe_ffdc_handler.cpp
+++ b/extensions/openpower-pels/sbe_ffdc_handler.cpp
@@ -41,6 +41,20 @@
using namespace phosphor::logging;
+constexpr uint32_t sbeMaxFfdcPackets = 20;
+constexpr uint32_t ffdcPkgOneWord = 1;
+const uint16_t ffdcMagicCode = 0xFFDC;
+
+typedef struct
+{
+ uint32_t magic_bytes:16;
+ uint32_t lengthinWords:16;
+ uint32_t seqId:16;
+ uint32_t cmdClass:8;
+ uint32_t cmd:8;
+ uint32_t fapiRc;
+} __attribute__((packed)) fapiFfdcBufType;
+
SbeFFDC::SbeFFDC(const AdditionalData& aData, const PelFFDC& files) :
ffdcType(FFDC_TYPE_NONE)
{