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
<clever> CarlFK1: ive now added network drivers to the arm bootloader, and it fails
jcea has quit [Ping timeout: 246 seconds]
<CarlFK1> clever: drivers = something the os can use?
<clever> CarlFK1: these drivers are just for the firmware, linux already has working drivers
<CarlFK1> entirely over the network - isnt that tftp, thus you have an ip stack?
<clever> yep, LWIP
<CarlFK1> https://github.com/lwip-tcpip/lwi 404. some secret repo? :o
<clever> oops
<jn> +p i guess
<clever> copy/paste fail
vriska has quit [Ping timeout: 248 seconds]
leo60228 has joined ##raspberrypi-internals
Ad0 has quit [Ping timeout: 272 seconds]
Ad0 has joined ##raspberrypi-internals
jcea has joined ##raspberrypi-internals
jcea has quit [Ping timeout: 252 seconds]
jcea has joined ##raspberrypi-internals
<CarlFK1> does RUN stand for something?
<CarlFK1> and where are some docs about it. I remember reading something, can't find it now
<clever> CarlFK1: its just a reset pin, but its active low (in reset when low)
<clever> and its equally valid to say its a run pin, active high (the cpu runs when high)
<clever> some chip creators just name it the other way around