Hi,
I would add '-device e1000e,netdev=net1,bus=pcie.0 -netdev user,id=net1' and
check that an IP address is assigned to the interface.
Thanks for your review and suggestion.
I will add a test for the e1000e device on AST2600.
I also have a question regarding AST2700:
1. SDK v09.06 does not include a built-in e1000e driver.
We have switched to v09.07 now.
2. AST2700 A0 does not support PCIe RC.
Given these limitations, if we want to test e1000e on AST2700, can I only add a
test case for the AST2700 vbootrom?
I think we can limit the test to AST2700 A1 since A0 should be removed.
1. The AST2700 FC SDK is still on v09.06 and cannot be upgraded to v09.07 until
the following patch series is applied:
https://patchwork.kernel.org/project/qemu-devel/cover/20250717034054.1903991-1-jamin_...@aspeedtech.com/
v09.07 is merged already and the series above needs a large rework
of the coprocessor models.
2. The manual device loader cannot be updated to SDK v09.07 because of this
commit
https://github.com/AspeedTech-BMC/openbmc/commit/17f7a259f3a4d052b9ea93353a3400040f39992e
Starting from SDK v09.07, u-boot-nodtb.bin is no longer shipped.
If we want to support it, we can generate it manually with the following
commands:
dumpimage -T flat_dt -p 0 -o u-boot-nodtb.bin u-boot.bin
dumpimage -T flat_dt -p 1 -o u-boot.dtb u-boot.bin
However, I am not sure how to install the dumpimage tool in the test
environment.
Could you please give me any suggestion?
I am not sure I am following the constraints/requirements :/
As of today, ast2600-evb looks ok to me. May be work on that first.
Thanks,
C.
