solrize has quit [Remote host closed the connection]
lagash has quit [Ping timeout: 264 seconds]
torbjornsd has joined #riscv
BOKALDO has quit [Quit: Leaving]
torbjornsd has quit [Ping timeout: 260 seconds]
smartin has joined #riscv
BOKALDO has joined #riscv
olofj has quit [Ping timeout: 264 seconds]
olofj has joined #riscv
jacklsw has joined #riscv
torbjornsd has joined #riscv
hexteex has quit [Remote host closed the connection]
lagash has joined #riscv
hexteex has joined #riscv
Andre_H has joined #riscv
cousteau_ has joined #riscv
hexteex has quit [Quit: Leaving]
jcm has quit [Ping timeout: 245 seconds]
khilman has quit [Ping timeout: 264 seconds]
jcm has joined #riscv
khilman has joined #riscv
smartin has quit [Remote host closed the connection]
smartin has joined #riscv
khilman has quit [Ping timeout: 265 seconds]
gatecat has quit [Ping timeout: 245 seconds]
jcm has quit [Ping timeout: 245 seconds]
khilman has joined #riscv
SanchayanMaity has quit [Ping timeout: 250 seconds]
jcm has joined #riscv
SanchayanMaity has joined #riscv
gatecat has joined #riscv
ornxka has joined #riscv
cousteau_ has quit [Quit: Bye! gotta go]
<ornxka>
i wrote -1 to mtimecmp but it didnt clear my interrupt
drmpeg has quit [Ping timeout: 250 seconds]
<ornxka>
it clears when i write 0xFFFFFFFF to it.. is the problem that it has to write to the register multiple times in order to write the whole 64 bits to it, and that its triggering a new interrupt in the middle of that due to having an intermediate value less than mtime?
Xark has quit [Ping timeout: 256 seconds]
drmpeg has joined #riscv
jacklsw has quit [Quit: Back to the real life]
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #riscv
Xark has joined #riscv
<ornxka>
>For RV64, naturally aligned 64-bit memory accesses to the mtime and mtimecmp registers are atomic.
<ornxka>
guess not
Xark has quit [Ping timeout: 245 seconds]
Xark has joined #riscv
X-Scale has quit [Ping timeout: 245 seconds]
X-Scale` has joined #riscv
<ornxka>
disabling interrupts, setting mtimecmp to -1, and then enabling them again also triggers a timer interrupt..
X-Scale` is now known as X-Scale
nvmd has joined #riscv
torbjornsd has quit [Ping timeout: 268 seconds]
torbjornsd has joined #riscv
BOKALDO has quit [Quit: Leaving]
Andre_H has quit [Ping timeout: 256 seconds]
gioyik has joined #riscv
nvmd has quit [Quit: Later, nerds.]
<sorear>
mtimecmp might be treated as signed on your platform, try writing 0x7F....FF to it