Filip Lewiński
Filip Lewiński
[Added](https://github.com/Dasharo/coreboot/pull/615/commits/d79cb186276f2c6e3bb1cefb0b93d918b9f995b6) Kconfig option
superseded and merged in a different PR
@mkopec https://github.com/Dasharo/coreboot/pull/643/commits/eafd734cfbbf672273c646e6f31ef68a4bfcf706
So the platform is operational, but only with vboot disabled. I thought to separate the effort we could review and merge in this state, then I could work on vboot...
V560TU bricked after changing settings, during `NBA001.001 Network Boot` * Test enters setup menu, enables network boot * After reboot the no battery prompt popped up in the top left...
Reproduced again, with the same test. Binary dump: [brick.zip](https://github.com/user-attachments/files/22136301/brick.zip Tried to analyze with `romscope`: ``` λ ./romscope compare ../brick_copy ../dcu/working_read.rom ===== Preparation ===== Extracting file /home/flewinski/workspace/rc6testing/brick-analyze/brick_copy Extracting file /home/flewinski/workspace/rc6testing/brick-analyze/dcu/working_read.rom =====...
I've just managed to reproduce this manually, by enabling the non-functional DMA protection option prior to toggling Network Boot back and forth. This seems to be what the automatic full...
IIRC, DMA protection is currently off-limits since there problem is within the Intel FSP for Meteor Lake, and we're not legally able to redistribute modified FSP. So we must wait...
This needs further testing and debugging on our side.
Probably related: https://github.com/Dasharo/dasharo-issues/issues/1100