freenode/#mezzano - IRC Chatlog
Search
14:37:14
varjag
froggey: is there any way to print system output in a repl session rather than serial
16:20:41
froggey
leo_song: right. drivers aren't currently notified when their devices go away, so any worker threads end up hanging around forever
16:22:04
froggey
johnjay: arm64 support has bitrotted, first step would be getting it running in qemu again
16:22:42
johnjay
froggey: ok. i tried doing qemu-system-arm -M help to see what the raspi code is on windows
16:22:44
froggey
after that you'd have to write platform drivers for the rpi. interrupt controller and timer support at least
16:24:04
housel
Another challenge for raspi support would be the necessity of talking to the GPU over the mailbox interface
16:25:43
johnjay
housel: i tried going to raspberrypi.org for documentation about that, but i found... not much
16:25:59
housel
The GPU is actually the first processor to boot, then it loads the kernel and starts up the ARM
16:26:49
froggey
qemu-system-aarch64 -machine virt -cpu cortex-a53 -kernel tools/kboot/kboot-qemu-arm64.elf -serial stdio -m 1G -device virtio-gpu-device -device virtio-keyboard-device -device virtio-mouse-device -drive if=none,file=path/to/disk.vmdk,id=blk -device virtio-blk-device,drive=blk -netdev user,id=vmnic,hostname=qemu -device virtio-net-device,netdev=vmnic
16:27:00
johnjay
froggey: it says kboot boots a linux kernel, you're using a linux kernel for testing?
16:39:21
johnjay
nice. i probably need to know more tools that are outdated so i can manually compile them
18:07:40
froggey
varjag: changing sys.int::*cold-stream* will catch some system output, but not the really low-level stuff
18:08:49
froggey
you can also boot with the video console enabled, that'll blast all output directly onto the screen. that's not really a great option though
18:13:08
varjag
i want to tweak network-card code a bit to show how you can e.g. capture packet data on a live system
18:20:01
froggey
it automatically creates a repl for any thread that uses the global *terminal-io*, instead of sending output to the serial port
18:21:23
froggey
can be a bit annoying because you end up getting windows for all kinds of stuff, like the keyboard worker complaining that it doesn't understand a certain key
18:22:47
froggey
or you could create your own popup-io-stream and have your messages write directly to it instead of *standard-output*
18:40:18
froggey
oh right, yeah. you should be fine with the regular one if you're outputting directly to it
19:22:29
froggey
do you want to try updating swank to use the new api? then the old *server-alist* stuff can be removed entirely