norly has quit [*.net *.split]
joerg has quit [*.net *.split]
lexik has quit [*.net *.split]
elastic_dog has quit [*.net *.split]
norayr has quit [*.net *.split]
danielinux has quit [*.net *.split]
danielinux has joined #maemo-leste
lexik has joined #maemo-leste
norly has joined #maemo-leste
_j has joined #maemo-leste
_j is now known as joerg
elastic_dog has joined #maemo-leste
Pali has quit [Ping timeout: 248 seconds]
Keeblo has joined #maemo-leste
Keeblo has quit [Remote host closed the connection]
pere has quit [Ping timeout: 252 seconds]
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
macros_ has quit [Ping timeout: 248 seconds]
macros_ has joined #maemo-leste
pere has joined #maemo-leste
mardy has joined #maemo-leste
<freemangordon> Wizzup: do you mind if I add PVR_GLES2_EXTENSION_APPEND env var in pvr driver?
uvos__ has joined #maemo-leste
norayr has joined #maemo-leste
uvos has joined #maemo-leste
Pali has joined #maemo-leste
uvos__ has quit [Ping timeout: 268 seconds]
xmn has quit [Quit: xmn]
xmn has joined #maemo-leste
<Wizzup> freemangordon: why would I mind?
<uvos> the bettery question is why is is nesscary, the normal mesa override envvars cant be used for mighty17[m]'s usecase?
<freemangordon> no
<freemangordon> pvr driver does not use those
<uvos> not sure why you could not add MESA_EXTENSION_OVERRIDE support but can add some other envvar
<uvos> seams wierd
<uvos> but if it is so..
<freemangordon> uvos: because adding support for that requires a complicated parser/logic
<freemangordon> it is in shape of MESA_EXTENSION_OVERRIDE=+EXT_1,-EXT_2, etc
<uvos> sure but the parser in mesa is used by all drivers, i gues the way the pvr dri driver is implemented makes it impossible to use common mesa functionallity
<freemangordon> yes
<uvos> then its fine, but not ideal ofc
<uvos> (to add a custom envvar)
<freemangordon> glGetString is in the blob
<freemangordon> and extensions are const string there
<uvos> just remove it
<freemangordon> remove what?
<uvos> glGetString from the blob
<uvos> why use that symbol
<uvos> (instead of implmenting a foss clone)
<freemangordon> umm... I am not sure I understand
<freemangordon> because it is used for more stuff then just GL_EXTENSIONS
<freemangordon> *than
<uvos> im just suggesting that maybe you could intercept the symbol and implement it in foss somewhere, (ie just re this one function)
<uvos> its just a suggestion for a alternative solution
<freemangordon> this is what I do (intercept)
<uvos> ok
<freemangordon> but, I care only about GL_EXTENSIONS case
<freemangordon> and leave the others to the blob
<uvos> ok
<Wizzup> I'm up for a more simple solution since realistically this will never end up in mainline mesa
<Wizzup> (since it relies on blobs)
<uvos> what about MESA_GLES_VERSION_OVERRIDE btw
<uvos> might be usefull to force gles 1 on occasion
<uvos> (if simple to implement on the way)
<freemangordon> uvos: this might be already supported, no idea
akossh has joined #maemo-leste
akossh has quit [Read error: Connection reset by peer]
akossh has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
norayr has left #maemo-leste [Error from remote client]
<freemangordon> ugh, es2info has a resource leak
noidea_ has quit [Remote host closed the connection]
noidea_ has joined #maemo-leste
noidea_ has quit [Quit: Leaving]
noidea_ has joined #maemo-leste
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
xmn has joined #maemo-leste
yanu has quit [Read error: Connection reset by peer]
yanu has joined #maemo-leste
xmn has quit [Quit: xmn]
<freemangordon> uvos: execute 'run-standalone.sh notify-send -t 30000 -c "chat-message" "hello" "message body"' couple of times
<freemangordon> if you come up with a grouping logic without specifying category, I will implement it
norayr has joined #maemo-leste
Livio has quit [Ping timeout: 268 seconds]
Twig has joined #maemo-leste
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
<uvos> you could group by pid i gues
<uvos> (it maybe not that great)
<uvos> honestly i would just ignore the grouping problem for now and fix it by adding a real que at some point
pere has quit [Ping timeout: 244 seconds]
<Wizzup> uvos: btw, if the call is hang up by the remote side, or by us even, it would be good to keep the call window around for another 5s or so
<Wizzup> currently it just disappears right away
<uvos> yeah i know
<Wizzup> iirc the maemo phone also gives indications using the notification bar at the top
<Wizzup> "call ended" or stuff like that
<uvos> notification bar?
<uvos> what notification bar? the toast message system?
<Wizzup> I don't know what that is, but it's a horizontal bar that stretches the screen but is not very high
<Wizzup> and it's mostly at the top of the screen
<uvos> like the battery low message?
<uvos> thats a toast notification
<Wizzup> yes
<Wizzup> those
<uvos> id rather use a low timeout libnotify notification
<uvos> (as that works cross platform) but ok
norayr has left #maemo-leste [Error from remote client]
Twig has quit [Remote host closed the connection]
mardy has quit [Quit: WeeChat 2.8]
akossh has quit [Quit: Leaving.]
Pali has quit [Ping timeout: 260 seconds]
norayr has joined #maemo-leste
<Wizzup> uvos: ping on my sphone changes
pere has joined #maemo-leste
<Wizzup> should I make a pr?
<Wizzup> hm, did I not push it?
* Wizzup checks
<Wizzup> Ah, no, it's fine, I squashed/rebased
<uvos> Wizzup: what should i be looking at?
<uvos> a pr is better to get my attetion
<uvos> im not going to follow what you do in your branches
<uvos> wip-rtcom is nolonger wip i gues?
<Wizzup> yeah
<Wizzup> I'll make a PR now
<Wizzup> note that the <unkown> to <unknown> change will also affect dbs
<Wizzup> actually probably not, nvm
norayr has left #maemo-leste [Error from remote client]
uvos has quit [Ping timeout: 268 seconds]
Livio has quit [Ping timeout: 268 seconds]
xmn has joined #maemo-leste