On 5 May 2017 at 11:21, Philipp Tomsich <philipp.toms...@theobroma-systems.com> wrote: > With our efuse driver for the RK3399 ready, we can add the > board-specific code that consumes the cpuid from the efuse block and > postprocesses it into the system serial (using the same CRC32 based > derivation as in Linux). > > We expose the cpuid via two distinct environment variables: > serial# - the serial number, as derived in Linux > cpuid# - the raw 16 byte CPU id field from the fuse block > > Signed-off-by: Philipp Tomsich <philipp.toms...@theobroma-systems.com> > --- > > Changes in v3: None > Changes in v2: None > > board/theobroma-systems/puma_rk3399/puma-rk3399.c | 79 > +++++++++++++++++++++++ > include/configs/puma_rk3399.h | 6 ++ > 2 files changed, 85 insertions(+)
Acked-by: Simon Glass <s...@chromium.org> But don't you want to use the same mechanism to make sure you get the right misc driver? _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
