[Skiboot] [PATCH 0/7] Abstract architectures for external tools

Stewart Smith stewart at linux.vnet.ibm.com
Fri Aug 14 16:29:10 AEST 2015

Cyril Bur <cyril.bur at au1.ibm.com> writes:
> Over the course of development and improvement of the tools kept within the
> skiboot repository it has become clear that the external tools could be run
> on something other than POWER (or ARM for BMC related tools). There is no
> fundamental reason why this is not possible, it is quite simple, however
> the difficulty was abstracting away the details of each architecture so that
> something generic could exist, the external tools which tried this
> independently were duplicating a lot of effort.
> Important considerations were:
> When running on a BMC pflash should be able to flash both the host and the
> BMC flash. The gard tool hasn't been updated to run on the BMC, I'm not
> sure it will need to be.
> When running on POWER pflash should be able to flash using the MTD device
> (and not the lpc) interface in order to limit the chance of concurrent
> access. The gard tool on POWER should be able to perform all its function
> including clearing gard records.
> On x86 both the pflash and the gard tool should still perform most of their
> functions, parsing, showing, modifying but with files on disk.
> Cyril Bur (7):
>   libflash: Return a pointer to internal structure.
>   libflash: Reintroduce typesafety in lowlevel libflash calls
>   external/common: Create common code for initialising libflash
>     components
>   external/common: Add POWERPC code reenable building pflash for POWER
>   external/common: Add x86 code reenable building pflash
>   external/pflash: Update distclean make target
>   external/common: Write an includeable rules.mk.

Something in this series seems to break 'make dist' for pflash.

More information about the Skiboot mailing list