On 22. 10. 19 1:46, Simon Glass wrote:
Hi Michal,
On Mon, 14 Oct 2019 at 07:29, Michal Simek michal.simek@xilinx.com wrote:
From: Siva Durga Prasad Paladugu siva.durga.paladugu@xilinx.com
This patch adds support for fru commands "fru capture" and "fru display". The fru capture parses the FRU table present at an address and stores in a structure for later use. The fru display prints the content of captured structured in a readable format.
As of now, it supports only common header and board area of FRU. Also, it supports only English language code and ASCII8 format.
fru_data variable is placed to data section because fru parser can be called very early before bss is initialized. And also information needs to be shared that's why it is exported via header.
Signed-off-by: Siva Durga Prasad Paladugu siva.durga.paladugu@xilinx.com Signed-off-by: Michal Simek michal.simek@xilinx.com
MAINTAINERS | 3 + cmd/Kconfig | 8 ++ cmd/Makefile | 1 + cmd/fru.c | 68 +++++++++++++ common/Makefile | 1 + common/fru_ops.c | 247 +++++++++++++++++++++++++++++++++++++++++++++++
Can we get some tests for this file?
We can generate one fragment, capture it and display it back. That should cover it. What way do you suggest to use? File/testing command?
Thanks, Michal