daynaport: record the two-driver verification; fail loudly on a missi… - #82
Merged
Merged
Conversation
…ng --config The DaynaPort target is now verified end to end against both IRIX drivers (irixdayna), with no changes needed to the emulation itself: rung IRIX 6.5 IRIX 5.3 detected dp0 at SCSI id 3 dp0 at scsi(0) target 3 lun 0 MAC read yes 00:80:19:44:50:03 ARP resolved resolved ping replies valid, 0 bad cksums 4/4, 0% loss TCP RST received RST -> connection refused So the record format and its CRC accounting, RETRIEVE STATS, ENABLE, SET INTERFACE MODE and the WRITE path all hold up against an independent implementation of the other end. Both drivers needed fixes of their own to get there (see irixdayna 3b9ab26 and c4b328d); none of them were here. Also: exit with an error when --config names a file that does not exist. A missing iris.toml is still fine - that is the "just run it" path - but a config the user named explicitly and that isn't there was silently booting a DEFAULT machine instead: different disks, no DaynaPort, none of what they configured. That cost a full 12-minute build-and-boot cycle to notice, because the relative path was resolved against a different cwd. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ng --config
The DaynaPort target is now verified end to end against both IRIX drivers (irixdayna), with no changes needed to the emulation itself:
rung IRIX 6.5 IRIX 5.3
detected dp0 at SCSI id 3 dp0 at scsi(0) target 3 lun 0
MAC read yes 00:80:19:44:50:03
ARP resolved resolved
ping replies valid, 0 bad cksums 4/4, 0% loss
TCP RST received RST -> connection refused
So the record format and its CRC accounting, RETRIEVE STATS, ENABLE, SET INTERFACE MODE and the WRITE path all hold up against an independent implementation of the other end. Both drivers needed fixes of their own to get there (see irixdayna 3b9ab26 and c4b328d); none of them were here.
Also: exit with an error when --config names a file that does not exist. A missing iris.toml is still fine - that is the "just run it" path - but a config the user named explicitly and that isn't there was silently booting a DEFAULT machine instead: different disks, no DaynaPort, none of what they configured. That cost a full 12-minute build-and-boot cycle to notice, because the relative path was resolved against a different cwd.