19:57 <somlo> geertu: ping

19:59 <somlo> geertu: trying to figure out the difference between when `pahole` tells me useful things about driver data structure layout (i.e., when I compile a litex-rocket 64-bit kernel) and when it gives up and says "file <foo.o> has no supported type information" (like when I compile a 32-bit vexriscv kernel, or a 64-bit intel one)

19:59 <somlo> am I missing some kernel CONFIG setting that enables some sort of additional debugging symbols being added to the driver .o files?

20:01 <somlo> same for a 32-bit intel kernel :(

20:02 <somlo> funny/weird thing is, I have absolutely no earthly idea why it actually works on my 64-bit risc-v kernel :)

21:05 <somlo> geertu: to answer my own question -- `pahole` needs the .o to be compiled with `-g`, it's that simple :)

21:50 <amstan> anyone have an arty a7? what does the linux support look like for the ARM core? I would really like to play with litex and perhaps make linux drivers for more of the litex ip blocks

21:51 <amstan> i considered the de10 nano, but it's out of stock

21:51 <bjonnh> I have an arty z7

21:51 <bjonnh> but it is painful to not have the uart on the fpga

21:52 <bjonnh> the a7 is likely much easier to work with