jr-logbot` has quit [Remote host closed the connection]
jr-logbot has joined #maemo-leste
lexik has quit [*.net *.split]
StephanvanSchaik has quit [*.net *.split]
lexik has joined #maemo-leste
StephanvanSchaik has joined #maemo-leste
xmn has quit [Ping timeout: 265 seconds]
joerg has quit [Ping timeout: 264 seconds]
joerg has joined #maemo-leste
adc has quit [Quit: reboot]
adc has joined #maemo-leste
<freemangordon>
pvr_drv seems to be dead-end too, IIUC it was written for omapfb
pere has quit [Ping timeout: 240 seconds]
mardy has joined #maemo-leste
pere has joined #maemo-leste
<tmlind>
fremangordon: not sure i ever tried glmark-es2-drm on droid4, only the wayland version
<tmlind>
freemangordon: not sure it helps, but the 2d blit is implemented in the kernel for psb500, git grep -e PSB_RSGX32 -e PSB_WSGX32 drivers/gpu/drm/gma500/
<Wizzup>
freemangordon: written for omapfb in the sense that it takes specific handles to pixmaps or something?
DPA has quit [Ping timeout: 245 seconds]
DPA has joined #maemo-leste
inky_ has joined #maemo-leste
_inky has quit [Ping timeout: 260 seconds]
inky has quit [Ping timeout: 264 seconds]
_inky has joined #maemo-leste
elastic_dog has quit [Quit: elastic_dog]
elastic_dog has joined #maemo-leste
uvos has joined #maemo-leste
jr-logbot has quit [Remote host closed the connection]
<uvos>
freemangordon: maybe you sould be looking at omap_pvr for xf86-video-omap
<uvos>
since thats the pvr module for the kms/drm omap ddx
jr-logbot has joined #maemo-leste
<uvos>
i remember having omap_pvr.so for omap4/ddk1.9 somewhere
<uvos>
but im not finding it rn
inky_ has quit [Ping timeout: 258 seconds]
inky_ has joined #maemo-leste
<freemangordon>
Wizzup: in the sense that it calls functions like PVR2DGetFrameBuffer
<freemangordon>
which are missing in ddk 1.17
<freemangordon>
uvos: started doing that, immediately hit missing PVR2DUpdateEventReq
<uvos>
:(
<freemangordon>
uvos: btw, do you know if there is 'upstream' version of that?
<uvos>
i got it from some ti repo
<uvos>
but i cant find it rightnow
<uvos>
might be some version of the sdk
<uvos>
or what do you mean by upstream?
<uvos>
for xf86-video-omap?
<freemangordon>
yeah, something like that
<uvos>
ok so for omap_pvr.so
<uvos>
im pretty sure it got it form a ti sdk archive
<freemangordon>
ah, so we don't have pvr accelerated exa?
<freemangordon>
hmm
<uvos>
no on d4 it uses software for all 2d
<uvos>
and only gles clients are 3d accelerated
<freemangordon>
but, woudn't that work with 1.17 as well?
<uvos>
yes
<uvos>
except that xf86-video-omap is dri2 only
<uvos>
so we would need to port it to dri3
<freemangordon>
ok, then I guess it makes sense to start from here and try to implement pvr exa, no?
<uvos>
yes
<freemangordon>
ah
<uvos>
thats what i was talking about on fr :P
<freemangordon>
oh, ok :)
<uvos>
and had you look at how the fallback path works
<freemangordon>
lots of things happened since :p
<uvos>
you reported it uses a special omapdrm ioctl
<freemangordon>
I more or less know them from glamor
<uvos>
to present
<freemangordon>
this is for dri2
<uvos>
right
<freemangordon>
for dri3 it should be standard
<uvos>
ok
<freemangordon>
sec to get my coffee
<uvos>
so updateing xf86-video-omap to dri3
<uvos>
and removing the glamor requirement for dri3 in modesetting
<uvos>
is essentaly equivalent
<freemangordon>
yes, but I would rather add dri3 to omap driver than trying to splict the can of worms modesetting is
<uvos>
sure
<freemangordon>
we need to find vendor driver that has dri3 support
<freemangordon>
do you know any other driver but modesetting?
<freemangordon>
that's foss that is
<uvos>
well -nouveau -ati and -intel
<freemangordon>
yeah, intel
<uvos>
-nouveau and -ati support dri3 without glamor
<uvos>
all of these are depricated tho
<uvos>
in favor of useing modesetting on everything
<freemangordon>
in favor of ms?
<uvos>
yes
<freemangordon>
hmm
<uvos>
ms is used universaly
<uvos>
amd havent updated xf86-video-amdgpu or xf86-video-ati in ages
<uvos>
and just tell everyone to use modesetting
<uvos>
intel still occaisonally updates -intel
<uvos>
but they also tell people to use modesetting often
<freemangordon>
tmlind: the point is that it used to work in 5.10, but is broken on 5.15 and I suspect your patch. Didn;t have time to test to revert it though, but will do ASAP
belcher has quit [Ping timeout: 268 seconds]
_inky has quit [Ping timeout: 245 seconds]
_inky has joined #maemo-leste
freemangordon has quit [Read error: Connection reset by peer]
freemangordon has joined #maemo-leste
cockroach has joined #maemo-leste
_inky has quit [Ping timeout: 258 seconds]
pere has quit [Ping timeout: 258 seconds]
_inky has joined #maemo-leste
inky_ has quit [Read error: Connection reset by peer]
inky has joined #maemo-leste
doc has quit [Ping timeout: 265 seconds]
<tmlind>
freemangordon: too many bugs, not sure which patch you need to test to revert..
doc has joined #maemo-leste
enyc has quit [Ping timeout: 246 seconds]
pere has joined #maemo-leste
pere has quit [Ping timeout: 258 seconds]
<Wizzup>
uvos: so shall I try to make it work on 5.10 then (kexecboot d3)
<uvos>
idk whats the trace related to mmc?
<uvos>
i would prefer lts 5.10 for clownboot anyhow
<Wizzup>
will need to dig it up
<Wizzup>
I am not sure if it is related to mmc
<uvos>
since dealing with the bootloader not working is no fun
<Wizzup>
right
<uvos>
i gues you can do 5.10 clownboot first
<uvos>
and then deal with brining up 5.15
<Wizzup>
ok
<Wizzup>
any patches I should throw on top of the lts that come to mind?
<Wizzup>
or shall I just try
<uvos>
no just keep it vanilla
<uvos>
we dont want patches interfering with 5.10.y either
<Wizzup>
k
<uvos>
other than your dts ofc
<uvos>
and the needed change for d3 in the cpcap driver
<uvos>
wrt regulators
<uvos>
ah wait
<uvos>
Wizzup: tmlind wanted the pstore patch in the bootloader kernel
<uvos>
because otherwise pstore is not preserved
<uvos>
that makes sense to add
<Wizzup>
got a link?
<uvos>
8eca717fce6b7c87b12b3a5b805cd0a2177598c5
<uvos>
in tmlinds pending kernel
<_inky>
what is pinephone's bluetooth driver? bluetoothctl tells me 'no default controller available'
<_inky>
that 'no default controller available'. :/
Pali has joined #maemo-leste
Danct12 has joined #maemo-leste
<_inky>
may it be i need some newer or older versions of that firmware?
Treebeard has joined #maemo-leste
Treebeard has quit [Changing host]
Treebeard has joined #maemo-leste
Treebeard is now known as BenLand100
BenLand100 has quit [Ping timeout: 252 seconds]
<_inky>
i solved it
<_inky>
needed to add user user to bluetooth group
<_inky>
should it be default for the user?
<_inky>
also, don't you want to add that pinephone bluetooth firmware repo as well
<_inky>
i just built deb from it and installed
<Wizzup>
_inky: yeah we haven't done much with bt yet
<Wizzup>
that should be a relatively simple fix though
akossh has joined #maemo-leste
<_inky>
so
<_inky>
should i ask to create a repo
<_inky>
and would you include that bt-firmware package by default?
<_inky>
also can you add to your scripts to automatically add user to bluetooth group?
<Wizzup>
not sure about the best approach for the former, maybe a pinephone-firmware package, and about the latter, yeah, I think parazyd can make that happen
<_inky>
and all devices need user 'user' to be a member of bluetooth group.
<_inky>
uvos: i see but there was no link to the firmware source, only to the package, and i added there as well this link. and it was not mentioned that user must be a member of bluetooth group.
<_inky>
btw now that i have bluetooth keyboard on pinephone, the only really dusturbing issue remains the display driver or display something, don't know.
<uvos>
that link is proubuly the wrong place to get the firmware
<_inky>
pinephone under maemo shouldn't be recommended to run people with epilepsy. the screen flickering can make healthy human to have headache.
<uvos>
freemangordon: btw the pinephone also would benifit from a dri3 without glamor ddx
Treebeard has joined #maemo-leste
Treebeard has joined #maemo-leste
Treebeard has quit [Changing host]
<uvos>
if you can make it generic
<uvos>
since gles2 glamor is buggy
<uvos>
and opengl on the pp is buggy
Treebeard is now known as BenLand100
<uvos>
and pp's driver needs dri3 too
<_inky>
yes please do something with it.
<uvos>
_inky: might happen as a by product of us working on the droid4
<uvos>
_inky: but it dont think we have the bandwith to tackle the pps driver bugs otherwise
<_inky>
my friend has pinephone and runs it under manjaro posh. obviously.
<_inky>
and it's veeeery slooooow
<_inky>
under maemo it's very fast, but has this screen driver issues.
<_inky>
under posh it becomes unresponsive often. under kde plasma too.
<_inky>
i think something is very wrong with plasma, and probably posh.
<uvos>
yeah this is desktop opengl support on being broken, you should complain to mesa people mostly
<uvos>
*on it
<_inky>
no i mean on maemo it is fast.
<uvos>
iirc
<_inky>
under maemo
<_inky>
it is very fast.
<_inky>
but yes, gfx bugs.
<uvos>
yeah sure thats unrelated
pere has joined #maemo-leste
<_inky>
because pinephone usually is used under wayland (posh and plasma i guess use wayland) i have no idea if someone works on something that may improve its graphics under x11.
<uvos>
afaik its not xorg per say but opengl the wayland wms use gles
<_inky>
droid 4 feels much faster and more usable only because of gfx drivers.
<uvos>
but i dont have one i just read the bugreports
<_inky>
i actually tried to understand this many times, but was not able.
<_inky>
so i understand opengl
<_inky>
as technology
<_inky>
and mesa as its implementation
<_inky>
and mesa can have implementation for different chipsets
<_inky>
right?
<_inky>
but what is egl, gles, gles2 etc?
<uvos>
right
<_inky>
also mesa can be used from both wayland and x11?
<uvos>
gles is different api tagentaly related to opengl
<uvos>
that is also implemented by mesa
<_inky>
oh
<uvos>
opengl|es
<uvos>
the wayland wms use that
<uvos>
x11 uses opengl proper
<_inky>
okay!
<uvos>
egl is a method of aquireing a surface to render on with opengl or gles
<_inky>
so i guess, when we'll have current debian in maemo, that will update mesa and may bring more fixes?
<uvos>
no
<uvos>
we have updated mesa allready
<_inky>
oh great.
<uvos>
you could maybe try mesa git
<_inky>
and is gallium something radeon related?
<uvos>
gallium is another low level api that mesa uses internally to allow drivers for different chips to only implement one api
<uvos>
so that a driver dosent need to implement opengl and gles (and directx too) but can just implement only a gallium driver
<uvos>
and the rest is generic wrappters that translate opengl -> gallium or gles -> gallium
<sicelo>
< _inky> pinephone under maemo shouldn't be recommended to run people with epilepsy. the screen flickering can make healthy human to have headache. :-D
<Wizzup>
uvos: mind if I keep the 'import <game>' open for now? most of them are pretty simple to solve (one is even just a missing icon in the app mgr)
<sicelo>
Wizzup: that's the one. it's not different. it's Tetris. inky - looks closed
<_inky>
eh.
<_inky>
parazyd: since you are here, not sure you've noticed what was before. one simple thing: user 'user' has to be part of bluetooth group by default.
<_inky>
s/part/member
<Wizzup>
inky: make it a part of the issue and assign parazyd is also a good practice
Danct12 has joined #maemo-leste
<uvos>
inky: ltris from debian repos works fine and plays great on d4
<uvos>
inky: needs kbd tho
<_inky>
uvos: thanks! i had emotional connection with maemo default one, even if it was crappier. (: but thanks, i'll try.
<_inky>
uvos: today i was playing frozen-bubble on pinephone and droid4. on pinephone it's impossible, on droid4 it is great.
<_inky>
well i was using hw kbd on pinephone.
<uvos>
eh ltris is not that great, for one thing it dosent scale at all and is fixed resolution
<uvos>
it happens fit the d4 display well
<uvos>
so it looks good on it
<uvos>
but otherwise....
<_inky>
Wizzup: i believe parazyd assigned the issue to himself already sometimes in 2020, and he may be doesn't know that the easy solution exists.
<_inky>
uvos: i'll try!
<Wizzup>
inky: what is the issue in question
<_inky>
as an offtopic i also have a tetris on my msx2 machine and sometimes play it.