Milestones
List view
This is the milestone where I implement `ps2client run [ --ee | --iop ] <some elf file>` - which internally boots the PS2, opens ps2link, and runs the elf file on the ps2. The elf file is expected to be found on the machine running ps2client, not on the ps2 itself.
No due date•0/1 issues closed* execiop * iopexcep * netdump * scrdump * listen (let's be real - listen is probably the first command I'll implement during 0.3 - but still needs covering off here) * dumpmem (probably this too - much more testable than execee)
No due date•6/11 issues closedWrite a `bin/execee` script that tells the PS2 to run a program, and captures the stdout/stderr/exit code from the usual udp listening port.
No due date•1/3 issues closedAdd a command `test [ --ee | --iop ] <some elf file>`, which opens a tcp listener, starts a test program and expects TAP output on the tcp port. The test command must exit 0 as well as pass all tests for the test to be considered successful
No due date•0/1 issues closed- No due date•1/4 issues closed
One of the great features of ps2client is its ability to present a filesystem to the PS2 as `host:` - to allow a program to be run using `ps2client execee host:program_file_name_here`. This milestone is complete when it is possible to get the PS2 to run a program from `host:`
No due date•4/12 issues closed* Write `bin/ps2client`, using the command-line framework of my choosing, and implement the `execee` command. * Get the execee command working, as close to the same as `ps2client`'s as possible, EXCEPT, no `host:` support.
No due date•0/3 issues closedAll the packet classes that need writing for full ps2link compatibility. This doesn't mean hooking up commands or logic to handle each class, just that each class is defined and can correctly (de)serialize packets.
No due date•9/25 issues closed