Máté Kukri uploaded patch set #9 to this change.
baytrail RFC: native replacement for refcode.elf
- This is a reverse engineered re-implementation of refcode.elf on Bay Trail
- What should be done with all the magic numbers?
- Is the ModPhy table considered data and can remain in a header or is it considered a blob and should be placed elsewhere?
- What is the "coreboot style" of doing all the MMIO access?
Signed-off-by: Mate Kukri <kukri.mate@gmail.com>
Change-Id: I91977c509022b0078804dc151d27296260e24bc4
---
M src/soc/intel/baytrail/Kconfig
M src/soc/intel/baytrail/Makefile.inc
M src/soc/intel/baytrail/include/soc/iosf.h
A src/soc/intel/baytrail/include/soc/modphy_table.h
M src/soc/intel/baytrail/include/soc/ramstage.h
M src/soc/intel/baytrail/iosf.c
A src/soc/intel/baytrail/modphy_table.c
A src/soc/intel/baytrail/refcode_native.c
8 files changed, 783 insertions(+), 33 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/33/43133/9
To view, visit change 43133. To unsubscribe, or for help writing mail filters, visit settings.