f_ changed the topic of ##raspberrypi-internals to: The inner workings of the Raspberry Pi (Low level VPU/HW) -- for general queries please visit #raspberrypi -- open firmware: https://librerpi.github.io/ -- VC4 VPU Programmers Manual: https://github.com/hermanhermitage/videocoreiv/wiki -- chat logs: https://libera.irclog.whitequark.org/~h~raspberrypi-internals -- bridged to matrix and discord
Stromeko has joined ##raspberrypi-internals
jcea has joined ##raspberrypi-internals
Stromeko has quit [Quit: Going… gone.]
Stromeko has joined ##raspberrypi-internals
jcea has quit [Ping timeout: 272 seconds]
angerisagift has quit [Ping timeout: 244 seconds]
angerisagift has joined ##raspberrypi-internals
angerisagift has quit [Ping timeout: 258 seconds]
angerisagift has joined ##raspberrypi-internals
jcea has joined ##raspberrypi-internals
radens has joined ##raspberrypi-internals
<radens> Hello there! I'm trying to write a microkernel for the rpi 1b (BCM2835). One issue I'm having is with the interrupt controller. I would like eg the sdhost driver to live entirely in user land, so how do I acknowledge interrupts once the fire before returning to user space?
<radens> It looks like the interrupt pending registers on the weird broadcom interrupt controller are read only
<clever> radens: i think the way thats generally done, is to mask the interrupt, and then drop to userland
<clever> and once userland ack's things, you can unmask the irq
<radens> that makes sense thanks
jcea has quit [Ping timeout: 248 seconds]