Do not truncate error log at runtime when using firmware_request
Do not truncate error log at runtime when using firmware_request

There is an implicit truncation in the path where we use
firmware_request to send an error log down to the FSP.  This
results in us sending a log full of zeros down instead of a
complete log because we didn't properly handle the flatten
error.  We were missing the argument to truncate, which is
required for both paths we use to send error logs.

Change-Id: Ie1a82841b33ee3d28f65d99f5707e249f2ca5a19
CQ: SW486880
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/93985
Tested-by: Jenkins Server <8e3f934e4c44875bc48d33da3ea13d93ba9a233f@us.ibm.com>
Tested-by: FSP CI Jenkins <aa9e4d9ac7cd25905e9c0dd36d4150516e73dd86@us.ibm.com>
Tested-by: Jenkins OP Build CI <e610bd72261d3c0a48f1e8ae36832ab00774d426@us.ibm.com>
Tested-by: Jenkins Combined Simics CI <8312af3886dfc9bb930f549023677220805b137e@us.ibm.com>
Reviewed-by: Daniel M Crowell <912029ca9254ac7b5854e56910561d682e1fa2d0@us.ibm.com>

open-power/hostboot,open-power/hostboot,open-power/hostboot,open-power/hostboot,open-power/hostboot