ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
<hanetzer> and I just realized I've been reading /topic this entire time; my mistake was "should be able to find a bar", as in, keep them away from t he booze :)
<hanetzer> so. that alcoholic screed out of the way; does mesa have a build system (docker/etc) I can use to build HEAD against for dev/testing purposes?
mbrost has quit [Read error: Connection reset by peer]
<icecream95> hanetzer: Oh, I always thought that was a reference to BAR (as in the "resizeable BAR" everyone is talking about these days), not an actual bar
<hanetzer> idk, maybe both lulz.
<hanetzer> my eyes see it in terms of booze, however :)
<kisak> the quote is older than the existance of resizable BAR
<HdkR> I always figured it was a bar of acceptable quality :P
<anholt_> but yeah, it was in reference to pci bars
<kisak> here I was under the impression that it was a life lesson to take a swig or two before digging into legacy code from X's era
nchery has quit [Quit: Leaving]
* hanetzer drank a fair bit while porting mesa to meson for gentoo :3
<hanetzer> there was some bug or another, forget who's fault, with buiding with USE=abi_86_32 on gentoo
jewins has quit [Ping timeout: 480 seconds]
<HdkR> What is abi 86_32? x32?
<hanetzer> means 32 bit libs on a 64 bit host.
<marex> hanetzer: what's the point of that ? :)
<marex> (cache utilization improvement?)
<kisak> HdkR: Gentoo portage supports multilib package compiling in the same environment. The end user gets to set ABI_X86="32 64 x32" (or removing any of those archs), which gets converted to a set of USE=abi_x86_xxx
<kisak> that's across most of the packages in portage as the common mechanism
<hanetzer> marex: well, some packages do not ship a 64 bit version at all (steam seems to be the primary offender tbh), so we tend to need 32bit versions of a handful of libs on amd64 gentoo machines (same for other distros tbh)
<hanetzer> like, the games under steam tend to have both 32 and 64 bit builds; but the actual steam client/launcher thingus is only available in 32bit.
<HdkR> kisak: Ah, so luckily not x32 :)
robmur01_ has joined #dri-devel
robmur01 has quit [Ping timeout: 480 seconds]
columbarius has joined #dri-devel
co1umbarius has quit [Ping timeout: 480 seconds]
dfip^ has quit [Ping timeout: 480 seconds]
mbrost has joined #dri-devel
dfip^ has joined #dri-devel
<hanetzer> ah actually the USE flag is abi_x86_{32,64,x32}
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #dri-devel
jhli has joined #dri-devel
agx has quit [Read error: Connection reset by peer]
agx has joined #dri-devel
ngcortes has quit [Remote host closed the connection]
azorshi has quit [Remote host closed the connection]
flto has quit [Ping timeout: 480 seconds]
mattrope has quit [Read error: Connection reset by peer]
<marex> sravn: could you pick https://patchwork.kernel.org/project/dri-devel/patch/20210713191633.121317-1-marex@denx.de/ ? It has AB/RB, it seems to have fallen through the cracks
flto has joined #dri-devel
boistordu has quit [Ping timeout: 480 seconds]
<clever> this is the latest render coming out of my rpi code
<clever> each line in the grid is 2 pixels thick, with a spacing of 20 pixels start to start (so 18 pixels of black)
<clever> the rpi logo, triangle, and text are each a seperate later, unrelated to the current issue, but acting as some references
<clever> there is then a 200x200 rect (filled with a mix of black, and transparent), that is mapped to /dev/fb0
<clever> though the transparent half isnt coming thru clearly
<clever> its top-left corner is located at 200,50
<clever> now that the grid is on, i can see that the black portion is 50 pixels tall
dllud has joined #dri-devel
dllud_ has quit [Read error: Connection reset by peer]
lemonzest has joined #dri-devel
<clever> ok, something is definitely screwy with this config
<clever> i pre-filled the framebuffer with pure red before launching linux
<clever> its still red now, but /dev/fb0 claims its not
<marex> clever: time to use the existing kernel driver for the vc4 ?
<clever> marex: nope, that fails due to async external abort
<clever> marex: you need a magic hangshake before the arm core is allowed to touch the 2d hardware, and i have yet to find it
<clever> but i did just find a decent clue
<clever> [root@nixos:~]# ramdumper 0x08000000 64
<clever> starting at 0x8000000 (128MB)
<clever> 0x08000000 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff |................|
<clever> marex: this is a custom util, that will mmap /dev/mem, and dump a chunk of physical memory
<clever> via that, i can see the solid green framebuffer, that the firmware had setup
<clever> [root@nixos:~]# hexdump -C /dev/fb0 | head
<clever> 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
<clever> *
<clever> 00006ac0 55 ff 55 00 00 00 00 00 00 00 00 00 00 00 00 00 |U.U.............|
<clever> marex: but, the /dev/fb0 created by linux, in response to the DT entry, is something else!
<marex> clever: well, print the address of the framebuffer in kernel and use print_hex_dump() there ?
<marex> clever: then you will know exactly what is in the framebuffer on boot
<clever> but thats also going to be a virtual addr in the kernel
<clever> and i need to know what phys addr it maps to
<marex> ioremap it, no ?
<marex> you know the PA, the PA is the PA of the framebuffer from which the vc4 is scanning data out to the rest of the display pipe, no ?
<clever> yeah
<clever> i know that 0x8000000 is the PA of the framebuffer
<clever> i configured it as such, and i can see the initial boot image in /dev/mem at that offset
<clever> drivers/video/fbdev/Makefile:obj-$(CONFIG_FB_SIMPLE) += simplefb.o
<clever> and that is the driver the compatible= i used matches to
<clever> drivers/gpu/drm/tiny/simpledrm.c: { .compatible = "simple-framebuffer", },
<clever> ah wait, it shows up in 2 drivers!
<clever> [root@nixos:/sys/devices/platform/system/8000000.framebuffer/graphics/fb0]# cat name
<clever> simpledrm
<clever> marex: and linux is using the other one!
<marex> clever: tinydrm is for those spi/i2c attached displays
<clever> CONFIG_DRM_SIMPLEDRM is what stole my node
idr has quit [Quit: Leaving]
<clever> marex: krnel rebuilt, and entirely bricked!
* clever whips out jtag
<marex> clever: is this drivers/video/fbdev/simplefb.c what you are trying to get operational ?
<clever> marex: that is the one i thought i was using, until just now
<clever> ive disabled the conflicting one, but that bricked the system, need to un-brick it first
<clever> i have dmesg logs once more!
<clever> not sure why it bricked, maybe a corrupt zImage copy?
<clever> [root@nixos:/sys/devices/platform/system/8000000.framebuffer]# ls -l
<clever> marex: that definitely changed the driver, this dir looks entirely different now
<clever> Documentation/ABI/testing/sysfs-devices-waiting_for_supplier: The /sys/devices/.../waiting_for_supplier attribute is only
<clever> and this file was not there before, *reads docs*
<clever> ah, /dev/fb0 doesnt exist anymore, nothing has claimed the DT node
mbrost has quit [Ping timeout: 480 seconds]
<clever> yep, CONFIG_FB_SIMPLE was off
<clever> marex: and i have a blinking cursor once more!!
macromorgan is now known as Guest6938
macromorgan has joined #dri-devel
Guest6938 has quit [Read error: Connection reset by peer]
<clever> and a login prompt!!
<clever> it versk!!!
<clever> marex: thanks to your questions, i realized there are 2 simple-framebuffer drivers, and found the one that works
<marex> clever: you should probably have that LCD checked, it doesn't look too healthy ;-)
<clever> marex: its a CRT tv
<marex> ;-)
<clever> because of the previously mentioned issues, the linux vc4 driver cant run
<clever> and i havent RE'd the hdmi init enough yet, to bring hdmi online
<clever> so i'm stuck with just ntsc out
<clever> marex: but it does look way way better, when i feed that ntsc into a proper lcd based screen
<clever> --- a/drivers/video/fbdev/core/bitblit.c
<clever> + printk("rendering %c to %d,%d\n", s[0], xx, yy);
<clever> marex: oh, thats a very bad idea, now that its working, infinite recursion!
mbrost has joined #dri-devel
shadeslayer has quit [Quit: Ping timeout (120 seconds)]
shadeslayer has joined #dri-devel
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
thellstrom1 has joined #dri-devel
dllud has joined #dri-devel
dllud_ has quit [Read error: Connection reset by peer]
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
thellstrom has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
i-garrison has joined #dri-devel
lemonzest has quit [Quit: WeeChat 3.2]
lemonzest has joined #dri-devel
jhli has quit [Remote host closed the connection]
mlankhorst has joined #dri-devel
Duke`` has joined #dri-devel
mbrost has quit [Remote host closed the connection]
danvet has joined #dri-devel
mmenzyns has quit []
sdutt has quit [Remote host closed the connection]
mmenzyns has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
dllud has joined #dri-devel
dllud_ has quit [Read error: Connection reset by peer]
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
Duke`` has joined #dri-devel
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
quasselcore has joined #dri-devel
quasselcore has quit [Read error: Connection reset by peer]
<pq> marex, sorry, I've no idea about Mesa internals.
quasselcore has joined #dri-devel
quasselcore has quit [Remote host closed the connection]
gouchi has joined #dri-devel
pcercuei has joined #dri-devel
mlankhorst has quit [Ping timeout: 480 seconds]
mlankhorst has joined #dri-devel
boistordu_ex has joined #dri-devel
Hi-Angel has joined #dri-devel
mmenzyns has quit []
mmenzyns has joined #dri-devel
yogesh_mohan has joined #dri-devel
dllud has joined #dri-devel
dllud_ has quit [Read error: Connection reset by peer]
camus has quit []
camus has joined #dri-devel
mlankhorst has quit [Ping timeout: 480 seconds]
camus1 has joined #dri-devel
camus has quit [Ping timeout: 480 seconds]
dllud_ has joined #dri-devel
dllud has quit [Remote host closed the connection]
dllud has joined #dri-devel
dllud_ has quit [Read error: Connection reset by peer]
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
shashanks has quit [Ping timeout: 480 seconds]
macromorgan is now known as Guest6957
Guest6957 has quit [Read error: Connection reset by peer]
macromorgan has joined #dri-devel
shashanks has joined #dri-devel
mlankhorst has joined #dri-devel
Company has joined #dri-devel
perr has joined #dri-devel
macromorgan is now known as Guest6958
Guest6958 has quit [Read error: Connection reset by peer]
macromorgan has joined #dri-devel
perr has quit [Quit: Leaving]
perr has joined #dri-devel
perr has quit []
smpl has joined #dri-devel
camus1 has quit []
co1umbarius has joined #dri-devel
columbarius has quit [Ping timeout: 480 seconds]
cphealy has quit [Remote host closed the connection]
<danvet> emersion, thx a lot for the pull, applied :-)
<danvet> also realized I had a commit here locally to remove the g+ links ...
<marex> pq: oh ... I thought you were one of the experts :)
<hanetzer> yeah man. the shorter the name the greater the expertise, this is a fact :P
azorshi has joined #dri-devel
<FLHerne> marex: pq is a windowing/Wayland/kernel ABI expert, just not a mesa one
<hanetzer> fair enough lol
<marex> FLHerne: ACK
iive has joined #dri-devel
Lucretia has quit []
sarnex_ has quit []
Lucretia has joined #dri-devel
sarnex has joined #dri-devel
hanetzer1 has joined #dri-devel
hanetzer has quit [Ping timeout: 480 seconds]
<daniels> hanetzer1: you can just look at any pipeline that's run in GitLab CI - those all execute in publicly-available Docker images
<daniels> hanetzer1: e.g. https://gitlab.freedesktop.org/mesa/mesa/-/jobs/13578327 tells you the container name in the first couple of lines of the job output; you can just pull that and execute the same stuff inside it
<sravn> marex: backlight patches go through Lee Jones <lee.jones@linaro.org> - backlight is not part of drm-misc although that would make total sense if it was
mlankhorst has quit [Ping timeout: 480 seconds]
sdutt has joined #dri-devel
azorshi has quit []
dllud has joined #dri-devel
dllud_ has quit [Remote host closed the connection]
boistordu has joined #dri-devel
boistordu_ex has quit [Ping timeout: 480 seconds]
flto has quit [Remote host closed the connection]
flto has joined #dri-devel
flto has quit [Remote host closed the connection]
flto has joined #dri-devel
illwieckz has quit [Ping timeout: 480 seconds]
lemonzest has quit [Quit: WeeChat 3.2]
illwieckz has joined #dri-devel
Daanct12 has joined #dri-devel
Danct12 has quit [Ping timeout: 480 seconds]
sdutt has quit []
cphealy has joined #dri-devel
thellstrom has joined #dri-devel
thellstrom1 has quit [Read error: Connection reset by peer]
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
dllud has joined #dri-devel
dllud_ has quit [Read error: Connection reset by peer]
quasselcore has joined #dri-devel
danvet has quit [Ping timeout: 480 seconds]
Duke`` has quit [Ping timeout: 480 seconds]
gouchi has quit [Remote host closed the connection]
ivyl has quit [Ping timeout: 480 seconds]
ivyl has joined #dri-devel
rossy has quit [Ping timeout: 480 seconds]
rossy has joined #dri-devel
bl4ckb0ne has quit [Ping timeout: 480 seconds]
bl4ckb0ne has joined #dri-devel
vyivel has quit [Ping timeout: 480 seconds]
vyivel has joined #dri-devel
imre is now known as Guest6984
imre has joined #dri-devel
vsyrjala has quit [Ping timeout: 480 seconds]
Guest6984 has quit [Ping timeout: 480 seconds]
vsyrjala has joined #dri-devel
dllud_ has joined #dri-devel
dllud has quit [Read error: Connection reset by peer]
quasselcore has quit [Read error: Connection reset by peer]
quasselcore has joined #dri-devel
Hi-Angel has quit [Ping timeout: 480 seconds]
iive has quit []