tree 4993655f587cd2c0b93d37e15cf8fec4841838cd
parent baba767eb00454c32ecf2888a047f5a3ccb2f3d3
author Patrick Venture <venture@google.com> 1572383116 -0700
committer Patrick Venture <venture@google.com> 1572384059 -0700

bugfix: frudevice: handle multi-record area

The multi-record area doesn't start with a leading header like the other
areas, so it needs to be handled differently.  It is comprised of
individual records each with their own 5 byte headers.  This processes
the multi-record area separately if it's detected.

Tested: Verified this properly handles the multi-record area by
independent FRU content validation from the returned IPMI response.
This is what was used to detect the bug in the first place.
Tested: Verified FRUs without the area are still processed fine.

Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: Ibd119a87d79ed71463e1dd62e1e1dfd0322e2268