ChanServ changed the topic of #panfrost to: Panfrost - FLOSS Mali Midgard & Bifrost - Logs https://oftc.irclog.whitequark.org/panfrost - <macc24> i have been here before it was popular
guillaume_g has quit [Ping timeout: 480 seconds]
guillaume_g has joined #panfrost
icecream95 has joined #panfrost
Daanct12 has joined #panfrost
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #panfrost
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #panfrost
Danct12 has quit [Ping timeout: 480 seconds]
Danct12 has joined #panfrost
Danct12 has quit [Ping timeout: 480 seconds]
nlhowell has joined #panfrost
Daanct12 has quit [Remote host closed the connection]
Danct12 has joined #panfrost
MajorBiscuit has joined #panfrost
Danct12 has quit [Quit: Leaving]
rasterman has joined #panfrost
<robmur01> icecream95: given what https://images.anandtech.com/doci/16694/GPU_24.png says, I'd imagine that native commands are ones that aren't emulated
rasterman has quit [Quit: Gettin' stinky!]
<icecream95> robmur01: Okay. I guess the iterators would interrupt the MCU upon seeing an unsupported opcode, which can then do whatever it needs to?
<icecream95> That would probably be easy to verify if I actually had hardware
<icecream95> Assuming that the debug printfs can be read from software...
<icecream95> It would be possible to mess with the firmware binary to change how printf works if needed, but that might be too close to binary reverse-engineering
<robmur01> I don't have access to the specs so this really is just me inferring rather than any wink-wink-nudge-nudge, but it seems logical - not unlike a microcoded CPU, indeed
<robmur01> which would presumably also answer the question of whether the command set is really rich enough to natively run the firmware which emulates the command set...
rasterman has joined #panfrost
<icecream95> robmur01: So far the only computational instruction I've seen is ADD. Maybe that's all that is natively supported?
<icecream95> Probably there is subtract as well, as ADD is 64-bit (I think) but has a 32-bit immediate
jernej has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
jernej has joined #panfrost
<icecream95> Hmm.. after Valgrind instrumentation of the Valhall blob, I see that it only uses four different locations from the CS user register pages
<icecream95> This sure beats using mprotect() to catch when the blob tries to read/write GPU memory
nlhowell has quit [Ping timeout: 480 seconds]
camus1 has joined #panfrost
camus has quit [Read error: Connection reset by peer]
icecream95 has quit [Ping timeout: 480 seconds]
jambalaya has quit [Remote host closed the connection]
jambalaya has joined #panfrost
pjakobsson has joined #panfrost
mriesch has joined #panfrost
nlhowell has joined #panfrost
Danct12 has joined #panfrost
nlhowell has quit [Ping timeout: 480 seconds]
Putti has joined #panfrost
Putti[l]_ has joined #panfrost
Putti[l]_ has quit []
MajorBiscuit has quit [Quit: WeeChat 3.5]
Putti has quit []
Putti has joined #panfrost
rasterman has quit [Quit: Gettin' stinky!]
<cphealy> Are there any tests that can be run with ARM GPUs using Panfrost IOCTLs via libdrm (without Mesa)? I looked in the libdrm source and don't see anything like AMD or Vivante have, but perhaps someone is aware of some not yet upstream code?
<cphealy> I'm looking for some basic tests that exercise the IOCTLs and simple command execution on the GPU.
<robclark> cphealy: i-g-t is probably the place to look
<cphealy> robclark: for exercising Panfrost GPU ioctls?
<cphealy> I thought IGT was more about DRM/KMS drivers
<robclark> gpu stuff too (although those are driver specific tests)
<cphealy> sounds good, I'll take a look.
<anholt_> yeah, igt would be the place for such tests to be put if they existed (but they likely don't)
rasterman has joined #panfrost
<robclark> there are a few panfrost tests in igt.. not sure if any of 'em actually run anything on gpu or if only ioctl tests
Putti[l]_ has joined #panfrost
Putti has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
Putti[l]_ has quit [Ping timeout: 480 seconds]