belcher has quit [Ping timeout: 252 seconds]
belcher has joined #maemo-leste
crab has quit [Ping timeout: 250 seconds]
n900 has quit [Ping timeout: 240 seconds]
crab has joined #maemo-leste
n900 has joined #maemo-leste
zhxt has joined #maemo-leste
joerg is now known as Guest4265
joerg has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
<freemangordon> uvos: Well, the dependency is not that tight, it is more or less like calling xdg stuff: https://pastebin.com/CiWmK7F4
<freemangordon> also, email client *does not* depend on calendar widget, but on a library that provides common ui elements
<freemangordon> it just happens that this library is part of calendar-ui, which I agree is a bad design
<freemangordon> however, maemo *is* hildon, like it or not, once we dehildonize it, it will be no more maemo but something else
zhxt has quit [Ping timeout: 244 seconds]
zhxt has joined #maemo-leste
<freemangordon> WTF is 'Pip' supposed to mean in PipCalendarDialog, PipCalendarColor and PipColorPicker?!?
sunshavi_ has quit [Remote host closed the connection]
sunshavi has joined #maemo-leste
<freemangordon> uvos: also, modest conditionally use color picker widget from calendar, it is #ifdef-ed
<freemangordon> this 'pip' drives me nuts, it is all over the place in calendar-ui, without a single hint what its meaning could be
<freemangordon> none of https://acronyms.thefreedictionary.com/PIP make any sense to me in the context. Anyways, I am going to rename it
<tmlind> so looks like weston-simple-dmabuf-egl works ok with current wlroots and gles2_texture_from_dmabuf_buffer works ok
<tmlind> looks like weston-simple-dmabuf-egl --drm-render-node=/dev/dri/card0 option is needed, otherwise it won't work. also needed for wlroots-0.14.0
<tmlind> so only weston-simple-egl is broken with current wlroots head, but works with wlroots-0.14.0
<tmlind> maybe fd confusion between drm cards as the renderer is a separate card
<tmlind> to me it looks like drmPrimeHandleToFD is not getting the right fd for weston-simple-dmabuf-egl
<tmlind> freemangordon, uvos: also glamor could get confused with the fd to use, worth checking
uvos has joined #maemo-leste
SpiderOnAFly has joined #maemo-leste
Dromyun has joined #maemo-leste
SpiderOnAFly has quit [Ping timeout: 245 seconds]
<uvos> glamor uses prvk dri device only
<uvos> or rather only the device you tell it to use
<uvos> if you specify omapdrm it works fine (in software rendering ofc)
<uvos> freemangordon: if its just calling it via dbus thats fine maybe, still a bit annoying for packaging (it should maybe just use modest if available at compile time) the problem for me with this being dependancies that for instance would later force us to port everything to gtk3 at the same time before anything works. that kind of thing is not acceptable
<uvos> like if to port the calendar ui or watever to gtk3 i have to also port modest which means i have to port abook and hildon-home and hildon-desktop and so pushing us into a corner where we have to port everthing at the same time. this makes mantaining these things nigh impossible since you cant test any componant untill you port everything, and the dependancie on hildonized gtk2 also makes incoperating these things in other distros
<uvos> impossible.
<uvos> so this kind of dependacy must be avoided imo
<uvos> as it would be taking us imo further away from maintainablity and also what would be my personal eventual goal that leste could cease to exist as a distrobution and simply be a project like kde or whatever that provides a ui/telephony/etc solution for distros to package along side all the other normal DE they pacakge.
xmn has joined #maemo-leste
zhxt has quit [Ping timeout: 252 seconds]
<Wizzup> uvos: yes the connui-cellular port is not ready yet for primetime
<Wizzup> uvos: libgofono was a bit hard to fit into the connui-cellular API
<uvos> Wizzup: i know, im just reporting
<uvos> Wizzup: the architecture of the status menu is simply bad, but thats another topic
<Wizzup> mhm
<Wizzup> I think it's not too bad tbh, but ok :p
<Wizzup> it's optimised for low resource usage
<uvos> yeah it was sane on n900 maybe
<Wizzup> uvos: you had more luck with another library for sfone, right?
<uvos> but i dont think its sane anymore
<uvos> Wizzup: anyhow maybe (if its not lots additional work) it might be worth it to ditch libgofono
<uvos> since we have to use something else anyways for all the interfaces libgofono dosent cover
<uvos> Wizzup: well intels libofono is feature compleate
<uvos> Wizzup: but i dident end up using it (rather i just used ofono directly) because it dident fit well with the way sphone worked
<uvos> so that was just less work
<Wizzup> I did quite some stuff but it wasn't ready yet https://github.com/maemo-leste/connui-cellular/commits/ofono-port
<uvos> ok
<uvos> using ofno directly is pretty sane, so is libofono or writing our own even
<uvos> we could also extend libgofono
<Wizzup> I need to look at what the exact problems were again, but I think I had to like call some glib event iteration functions to get the info from libgofono, since it took a while for it to process changes
<uvos> but libofono is very close in function (and glib usage)
<Wizzup> that kind of stuff
<uvos> ok
<uvos> i havent used libofono at all but its internals looked very sane (i lifted code for sphone)
<uvos> if you want to try that
<Wizzup> (this is for the pin entry iirc)
<uvos> ok
<Wizzup> you can tell by the commit msgs I was getting a bit annoyed
<Wizzup> however I currently have a strong hangover and I can't reason clearly about it :D
<Wizzup> I think once tor/wireguard is done (deadline in ~10 days), I will get back to audio, and then probably telepathy+cellular makes sense
<Wizzup> the commit msgs at least show how much had to be ported
<Wizzup> but basically it's currently full of hacks
Dromyun has quit [Quit: Quit]
<uvos> anyone having the problem that the leste kernel dosent shutdown properly?
<Wizzup> what device?
<uvos> i just booted it by accident
<uvos> d4
<uvos> my private dev kernel shuts down fine
<uvos> the leste one dose not
<Wizzup> I don't think so, could it be related to the new dsme?
<uvos> (5.11)
<uvos> new dsme isent tagged out or?
<Wizzup> it's in -devel afaik
<uvos> hm maybe the swtich in kernel came at the same time so yeah
<uvos> have to check
<uvos> hmm no its something with the kernel
<Wizzup> I don't think we upgraded the kernel recently did we?
<uvos> no but i havent used your kernel untill now
<uvos> i was just swiching from one i built to the vanilla leste one
<Wizzup> so what do you do, type 'sudo poweroff' and then it resets for you?
<uvos> it just hangs sudo power off hangs at a blank screen with just a _
<uvos> power off via dsme hangs with just the mce light on forever
<Wizzup> let me upgrade to latest sw and try
<uvos> works fine with the other kenrel
<uvos> (should be same thing except i have some wip cpcap patches and a call audio hack applied)
<Wizzup> could also potentially be related to new mce perhaps
<Wizzup> let's see
<uvos> i gues but i have been using that for a long time
<uvos> (with dev kernel ofc)
<Wizzup> at least before upgrade to latest mce and dsme 'poweroff' from terminal worked fine
<Wizzup> booting again
<Wizzup> uvos: not seeing any problems here
Daanct12 has joined #maemo-leste
Danct12 has quit [Ping timeout: 252 seconds]
<uvos> hmm wierd
<freemangordon> uvos: I agree, more or less, however, it is nopt now the time to start decoupling, lets first have something that works
<freemangordon> otherwise we'll never end chasing our tail
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 245 seconds]
<uvos> we need to create a ddk1.17 package
<uvos> for pure ddk
<uvos> this works for chomeos mesa
<uvos> but im trying to setup pure pvr again rn and the dependacy mess is maddening
<tmlind> yup.. so the dmabuf issues seem to be related to buggy mesa modifiers handling.. trying to fix
<tmlind> the chromeos mesa patches as in jonathan's tree do advertise modifiers, but it's buggy so currently disabled
<tmlind> the ddk-1.17 blobs don't even advertise modifiers which can cause issues guessing the format
<tmlind> uvos: yup that pvrsrvinit.c totally does the trick :)
Daanct12 has joined #maemo-leste
<tmlind> oh then i did get weston-simple-egl running too with a temporary test hack of sudo ln -s /dev/dri/card0 /dev/dri/renderD128 after starting sway..
Daaanct12 has quit [Ping timeout: 240 seconds]
<Wizzup> sounds like progressa
<tmlind> there's a bug somewhere where /dev/dri/card0 should be returned instead of the render device for dmabuf related ioctls..
<tmlind> yup getting there slowly
<uvos> tmlind: nice
<uvos> i cant get the pure blobs to work atm with our glbc for some reason (dosent want to load dri_pvr.so
<uvos> )
<uvos> Wizzup: found out why it was locking up with the mobile conui
<uvos> Wizzup: was not your or its fault
<uvos> but my fault and a wierd interaction
Pali has joined #maemo-leste
<Wizzup> uvos: ok
<lel> IMbackK opened a pull request: https://github.com/maemo-leste/hildon-desktop/pull/15 (avoid regesitering presence more than once to avoid lockup)
<uvos> freemangordon: ^^^^ is required 95ec1becd1a413a77609629ab4ce73f8c51db11a but not 758d2685c788b19cf71d17fc25d65cba025f7ddd otherwise causes a lockup in certain situations
inky_ has quit [Remote host closed the connection]
inky_ has joined #maemo-leste
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 245 seconds]
<kona> My n900 arrived! Time to party like it's 2009!
<Wizzup> :)
<Wizzup> kona: let me know if you'd like a d4 as well, I could ship you one in a few weeks
<kona> i haven't had any luck sourcing a d4. so maybe?
<kona> it's always fun to see what people leave on used devices.
<kona> in this case, email from 2010.
<freemangordon> uvos: not sure I understand the issue (no PR or commit description)
<uvos> hd_enumerate_input_devices can get called multiple times
<freemangordon> ah
<uvos> XSelectExtensionEvent multiple times has interesting effects
<uvos> (xorg hangs effectively)
<freemangordon> wel,, why is not that in the commit message? :(
<uvos> "avoid regesitering presence more than once to avoid lockup"
<uvos> i gues "avoid regesitering for presence event more than once to avoid lockup"
<uvos> would have been enough
<uvos> the fact that you can use XSelectExtensionEvent to wedge the xserver seams like a bug tho
<uvos> should maybe report it
<freemangordon> maybe, but please, for the future, please leave a sentence or 2 to explain what the issue is and how the commit fixes it, ok? example: https://github.com/maemo-leste/dsme/commit/d866deb122101cffec00620947843fea1396568f . See, I am not nitpicking, it is really way easier to review if you know what it is all about, without trying to guess.
<freemangordon> I think there is no use to raise a bug agains xorg
<freemangordon> they will silently ignore, most probably
<uvos> not if it affects xwayland :P
<freemangordon> hmm, right :)
<freemangordon> does it?
<freemangordon> BTW, what are the chances to run h-d on xwayland?
<freemangordon> in theory it should run, no?
<uvos> should exist
<uvos> the same extension exists
<uvos> yeah should run
<freemangordon> we shall try to start it someday
<uvos> but accelerated xwayland on d4 is hard/impossible
<freemangordon> glamor?
<freemangordon> isn't it the same as with ordinary x?
<uvos> there where other problems tmlind was investigating
<uvos> ask him
<freemangordon> maybe we shall follow the stream and focus on xwayland instead of trying to resurrect yet another dead man (xserver)
<freemangordon> (just thinking out loudly)
<uvos> maybe
<uvos> ultimately we need to replace h-d really
<uvos> but thats nigh impossible manpower wise ofc
<freemangordon> kona: BTW, I am on holiday starting tomorrow for a week
<freemangordon> so far you have wpeditor in the repo
<freemangordon> so you can install it
<kona> yes, it's installed for me :)
<freemangordon> I am going to fulfill another modest dependency when I am back
<freemangordon> calendar-widgets that is
<freemangordon> but for now you may simply remove it temporarily while I finish the REing
<kona> ok!
<freemangordon> if remove it from debian/control that is, configure.ac is already smart enough to deal with that
<freemangordon> basically, if there is no calendar-ui-widgets pkgconfig package, modest will use HildonColorPicker instead of PipColorPicker (pip_color_picker_select_color())
<freemangordon> Not that I know the difference :)
<freemangordon> also, it seems modest-providers-data is included as dependency, but not really used
<freemangordon> kona: one question - do you rewrite tinymail gnomevfs module with gio or do a copy of it to be ported to gio
<freemangordon> ?
<lel> freemangordon closed a pull request: https://github.com/maemo-leste/hildon-desktop/pull/15 (avoid regesitering presence more than once to avoid lockup)
<uvos> freemangordon: great
<kona> Rewrite was my plan, do you have a beret idea?
<uvos> freemangordon: please coordinate with parazyd on any release of h-d (as the prs require removals and changes to the meta packages)
<kona> s/beret/better/
<kona> Well, rename to libtinymail-gio
<kona> I don't plan to rename the tinyvfs apis, though
<freemangordon> kona: what about introduce a copy (libtinymail-gio) and to keep the current gnomevfs plugin
<freemangordon> It should be the same, no?
<freemangordon> besides that we'll keep it compatible with fremantle
<freemangordon> and yes, no tinyvfs rename shall be done
<freemangordon> uvos: I will, but I want to fix anotehr issue I just saw
<uvos> not that there is a reason not to but compatability with fremantle is fairly unimportant no?
<uvos> freemangordon: no rush
<uvos> freemangordon: im just saying that the old method of rotation needs to go at the same time on user devices :)
<freemangordon> why are those not static?
<uvos> oversight
<freemangordon> or rather - is there any particular reason?
<uvos> no
<freemangordon> ok, going to fix
<freemangordon> uvos: re tinymail - it is unimportant, but is more or less free
<uvos> ok
<uvos> yeah was just asking it as a policy question
<freemangordon> we just don;t build gnomevfs module for leste
<uvos> (ie is fremantle backward compatibilty a goal)
<freemangordon> besides fremantle, there are 4 or 5 more platforms that are supported
<freemangordon> includeing gnome desktop
<freemangordon> so we either remove them all and leave leste only or add leste as another platform
<freemangordon> I'd say - add leste as another platform given that wit costs no additional overhead
<freemangordon> *it costs
<uvos> sure im not opposed
<freemangordon> kona: what do you think?
<freemangordon> I have already added mamo-leste platform
<freemangordon> *maemo-leste
<freemangordon> uvos: back to h-d: don;t we have the same issue with DeviceMotionNotify() ?
<kona> Does tinymail even build for the others now?
<freemangordon> for sure it builds for fremantle
<freemangordon> and I see no reason to not build for others
<kona> Ah, hmm.
<kona> Ok, no problem :)
<uvos> freemangordon: no because XCloseDevice unregisters all notfiers on the device afaik
<freemangordon> though I am not sure we shall keep it backward compatible after leste is fully functional
<freemangordon> but until then...
<uvos> yeah thats fine
<uvos> no way that runs twice for the same device
<uvos> guards it with
<uvos> hd_close_input_devices
<uvos> and that calls XCloseDevice on every device
<freemangordon> basically we get (possibly) different xi_motion_ev_type value for every call, no?
<uvos> sure yeah you get it for the last device more or less
<uvos> thats "fine"
<freemangordon> ok, if you say so I am not going to argue, but it looks suspicious to me, like, why event id for the last device is the same as for the others?
<freemangordon> it is the same because the class is the same?
<freemangordon> *is it
<uvos> not sure if its defined to be so
<uvos> but it is in practice
<uvos> im reading docs rn to see what i can find
<freemangordon> ok
<freemangordon> going to fix those static vars in the meanwile
<freemangordon> uvos: have a look at FindTypeAndClass macro
<freemangordon> it seems it just happens to return the same values for different devices
<uvos> its allways the same
<uvos> type = _ip->event_type_base + offset
<uvos> offset is #define _deviceMotionNotify0
<uvos> and _ip->event_type_base is the same if device class is the same
<freemangordon> so, _ip is the same for every device?
<uvos> looks like yeah for same input_class
<uvos> let me check
<freemangordon> thanks
<uvos> it comes from a global here
<uvos> this really is an implementation detail of xorg
<uvos> but yeah it looks like its ok
<freemangordon> yup
<uvos> i gues a perfectly spec adhering x11 server could do something else
<freemangordon> ok, going to do a release
<Wizzup> thanks for being thorough guys
<freemangordon> uvos: will you have some spare time soon to look at matchboz focus (or whatever it was) issue?
<freemangordon> *patchbox
<freemangordon> aaah
<freemangordon> MATCHBOX
<freemangordon> :)
<uvos> freemangordon: sure
<uvos> rn im still trying to figure out why the pure pvr setup dosent work for me anymore
<uvos> yeah i dont get it so it goes:
<uvos> MESA-LOADER: failed to open pvr (search paths /usr/lib/dri)
<uvos> failed to load driver: pvr
<uvos> i can LD_PRELOAD=/usr/lib/dri/pvr_dri.so
<uvos> and then it works
<uvos> if i strace it goes openat(AT_FDCWD, "/usr/lib/dri/pvr_dri.so", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 4
<uvos> so
<uvos> not sure whats up with that
<uvos> freemangordon: any ideas?
<uvos> freemangordon: what to check even
<freemangordon> I think we must LD_PRELOAD, otherwise we have issue because of the hacked libc version
<uvos> thats not great
<freemangordon> I wonder it works at all even with LD_PRELOAD if you use stock (and not 'hacked') blobs
<freemangordon> sure it is not
<uvos> no
<uvos> ld will just fail immidatly
<uvos> because it checks the symbols
<freemangordon> so, those are hacked blobs?
<uvos> yeah
<freemangordon> ok, you have to LD_PRELOAD couple of them
<uvos> just usr/lib/dri/pvr_dri.so works fine
<freemangordon> won't work otherwise
<uvos> anyhow maybe we should try and solve the issues that chromeos mesa has
<uvos> as it needs nothing of the sort
<freemangordon> doesn;t it need the same blob?
<uvos> it uses some of the blobs
<uvos> but not that one
<uvos> see that
<freemangordon> so, same shit, they are linked to the newer libc6
<uvos> right
<uvos> but no LD_PRELOAD needed
<uvos> it just works after weaking the symbol versions
<freemangordon> hmm, okm
<uvos> since usr/lib/dri/pvr_dri.so is foss
<uvos> and compiled against whatever
<uvos> you want
<freemangordon> is it? ah. ok
<uvos> yeah
<uvos> (but it just loads the _MESA blobs
<uvos> )
<uvos> its just a wrapper
<uvos> but this is enough
<freemangordon> right
<freemangordon> but, where is the source code?
<freemangordon> oh, this is the whole mesa
<uvos> yeah the prv driver is in tree there
<uvos> it just loads libglslcompiler.so and libGLESvX_PVR_MESA
<uvos> no other blobs needed
<uvos> (well you need extra stuff for pvrsrvinit
<uvos> )
<freemangordon> right
<uvos> anyhow it has added issues
<uvos> i use this for wayland
<uvos> and for some reason glamor bails early because it dosent find a texture format it likes
<uvos> and glmark also dosent work
<freemangordon> hmm, weird
<uvos> weston/ sway and kmscube work fine
<uvos> so thats why i was trying to swtich
<uvos> but figureing iout why it dosent work might be better anyways
<uvos> since you can compile egl with x11 support using this
<freemangordon> gbm should work
<freemangordon> I am not sure you can, because x11 support was not compiled in the blobs
<uvos> well you can to the point that egl advertises it
<uvos> but no idea if it works
<uvos> since xorg dosent start at all
<freemangordon> it will not
<freemangordon> but anyway, it is too late here already and I am not sure I am of any use now :)
<uvos> ok
<freemangordon> so going to have some sleep
<uvos> but where dose the x11 platform go into the blobs
<freemangordon> in dri support
<uvos> since the compiled out part you investigated long ago was in egl
<uvos> ok
<uvos> so pvr_dri.so contains/needs support?
<freemangordon> dont; remember the details now, but every windowing system (WL,gbm, x11) has support in the blobs. x11 was compiled out
<uvos> yeah but that was (at least what you showed in re) in libEGL
<freemangordon> not pvr_dri
<uvos> thats no longer a blob
<freemangordon> ok, lemme check
<freemangordon> uvos: IIRC, in libgbm
<uvos> also not a blob
<freemangordon> uvos: libEGL
<uvos> right
<uvos> so theres a chance it would work
<freemangordon> no, lemme show you the code
<freemangordon> (decompiled)
<freemangordon> uvos: see PM
<freemangordon> but basically:
<freemangordon> if (WL) then plat = 2
<freemangordon> else plat = 1
<freemangordon> else if (GBM) then plat = 1
<freemangordon> so, only GBM and wayland
<freemangordon> the same is stated in release notes
<uvos> (note for others): the function in question is implemented in foss mesa code in the chomos patches route
<uvos> we dont know however if this means anything
<uvos> anyhow geting glamor to work for 2d accel on pure pvr blobs first makes sense
<uvos> since then we dont have to contend with the additional buggyness of chomeos mesa
<uvos> we can switch later
<freemangordon> uvos: h-d is build, night!
uvos has quit [Ping timeout: 256 seconds]
<kona> hmm. getting u-boot installed alongside maemo5 is proving to be unusually difficult.
<kona> looks like my 900 won't connect to my AP and when I try tethering to my phone the connection is unstable
<kona> ah, it's dns.
Pali has quit [Ping timeout: 245 seconds]