<html><body><p>I believe FSP PELs can be up to 64k. <br><br>I also believe the BMC code has a limit for the eSEL content to only be 2k. Hostboot truncates our PEL content to the eSEL limit when we send it to the BMC. <br><br>Patrick Williams<br><br>> On Aug 2, 2015, at 5:36 AM, Vasant Hegde <hegdevasant@linux.vnet.ibm.com> wrote:<br>> <br>> Currently we are assuming Max PEL size is 64K. But in reality log size<br>> much lesser than this. Hence reduce size to 16K...which is the max size<br>> we use in FSP based machine as well.<br>> <br>> Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com><br>> Cc: Alistair Popple <alistair@popple.id.au><br>> Cc: Jeremy Kerr <jk@ozlabs.org><br>> ---<br>> hw/ipmi/ipmi-sel.c | 2 +-<br>> 1 file changed, 1 insertion(+), 1 deletion(-)<br>> <br>> diff --git a/hw/ipmi/ipmi-sel.c b/hw/ipmi/ipmi-sel.c<br>> index cce4042..087ed97 100644<br>> --- a/hw/ipmi/ipmi-sel.c<br>> +++ b/hw/ipmi/ipmi-sel.c<br>> @@ -84,7 +84,7 @@ static struct oem_esel oem_esel = {<br>> * the possible presence of the user defined section). We chose this<br>> * size because it's what FSP uses, but we could probably reduce<br>> * it. */<br>> -#define MAX_PEL_SIZE 0x10000<br>> +#define MAX_PEL_SIZE 0x4000<br>> <br>> #define ESEL_HDR_SIZE 7<br>> <br>> -- <br>> 2.1.0<br>> <br>> _______________________________________________<br>> Skiboot mailing list<br>> Skiboot@lists.ozlabs.org<br>> <a href="https://lists.ozlabs.org/listinfo/skiboot">https://lists.ozlabs.org/listinfo/skiboot</a><br><BR>
</body></html>