| *** tpb <[email protected]> has joined #openrisc | 00:00 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC (Ping timeout: 240 seconds) | 05:10 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #openrisc | 05:14 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC (Ping timeout: 240 seconds) | 06:19 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #openrisc | 06:59 | |
| shorne | zx2c4: first test for the semihosting ABI, I created a proposal PR | 08:38 |
|---|---|---|
| shorne | https://github.com/openrisc/openrisc.github.io/pull/18 | 08:38 |
| shorne | I mean first step | 08:38 |
| shorne | In terms of Reset, I am wondering if we could instead just jump to 0x100 for example | 08:39 |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC (Ping timeout: 240 seconds) | 14:22 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #openrisc | 14:53 | |
| *** zx2c4_ <zx2c4_!sid204921@gentoo/developer/zx2c4> has joined #openrisc | 15:42 | |
| *** shorne_ <[email protected]> has joined #openrisc | 15:45 | |
| *** shorne <[email protected]> has quit IRC (*.net *.split) | 15:49 | |
| *** zx2c4 <zx2c4!sid204921@gentoo/developer/zx2c4> has quit IRC (*.net *.split) | 15:50 | |
| *** zx2c4_ is now known as zx2c4 | 15:50 | |
| *** Finde_ <[email protected]> has joined #openrisc | 15:53 | |
| *** Finde <[email protected]> has quit IRC (Read error: Connection reset by peer) | 15:53 | |
| *** Finde_ is now known as Finde | 16:49 | |
| zx2c4 | shorne_: woah awesome | 17:41 |
| zx2c4 | im wondering... while you're specing all this out, maybe you want to cut back on exactly what you spec at first? it's harder to claw things back once they're spec'd | 17:42 |
| zx2c4 | Like, perhaps just 1 shutdown and 1 reboot method? | 17:42 |
| zx2c4 | Jumping to a fixed address to reset, and then having QEMU hook this, would make sense, because it's something that hardware could implement to with the same method | 17:42 |
| zx2c4 | I think a few platforms do something like that | 17:43 |
| shorne_ | zx2c4: yeah, I was thinking too about implementing only a limited set of the nop operations. We use NOP_REPORT and NOP_PUTC a lot, so I would like to include those. | 21:31 |
| shorne_ | but others I have not really used before | 21:32 |
| shorne_ | zx2c4: what is your usecase for reset in your CI testing? | 21:33 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!