 and I am experimenting with a solution
<alf_> (well tentative solution)
<alan_g> alf_: well done
<alan_g> Guesses it was a race condition
<alf_> alan_g: well done to you too :)
<alf_> alan_g: https://code.launchpad.net/~afrantzis/mir/fix-gbm-udev-events-test/+merge/197182
<alan_g> alf_: ta
<pete-woods1> tvoss_: good afternoon / ping!
<tvoss_> pete-woods, hello :)
<alan_g> alf_: looking at greyback's hacks for qt composition reminds me that the lack of information about what changed when calling the notify_change is something we need to address. (In this case he's created a second callback so that he knows which surface has posted a buffer)
<greyback> alan_g: yep, I did that :)
 * alan_g thinks that a surface pointer in the notification would be useful for other use cases too
<alf_> alan_g: greyback: sure
<greyback> alan_g: alf_ these are misc notes I took in my work: https://docs.google.com/a/canonical.com/document/d/12aVPbX5qzr2GqF8yBcc17ZWsD9Z1kQfoSaYi2yMm1rE/edit
<greyback> They're rough, but I'd say they're of interest
<alf_> greyback: very useful, thanks
<alan_g> I'd also like to factor in the display on notification we were discussing re the GNexus problems
<alan_g> greyback: useful notes. I think there are some alternative solutions but knowing the problems is good.
<alf_> greyback: @generic way to call eglGetProcAddress(), can you please elaborate, it's not clear what's blocking us from using  eglGetProcAddress()
<greyback> alan_g: oh of course, I just hacked in what I needed
<greyback> alf_: I suppose nothing stops me calling eglGetProcAddress. Just didn't know if Mir should wrap it or not. Probably not..
<alan_g> sure,
and I am experimenting with a solution 
 < alf _ > (well tentative solution) 
 < alan_g > alf _: well done 
 < alan_g > Guesses it was a raceway circumstance 
 < alf _ > alan_g: well done to you too :) 
 < alf _ > alan_g: https://code.launchpad.net/~afrantzis/mir/fix-gbm-udev-events-test/+merge/197182 
 < alan_g > alf _: ta 
 < pete - woods1 > tvoss _: beneficial good afternoon / ping! 
 < tvoss _ > pete - woods, hello :) 
 < alan_g > alf _: looking at greyback's cab for qt composition reminds me that the lack of data about what change when call the notify_change is something we need to address. (In this case he's create a second callback so that he know which surface has posted a buffer zone) 
 < greyback > alan_g: yep, I did that :) 
  * alan_g thinks that a surface cursor in the notification would be useful for other use casing too 
 < alf _ > alan_g: greyback: sure 
 < greyback > alan_g: alf _ these are misc notes I took in my workplace: https://docs.google.com/a/canonical.com/document/d/12aVPbX5qzr2GqF8yBcc17ZWsD9Z1kQfoSaYi2yMm1rE/edit 
 < greyback > They're rough, but I'd say they're of interest 
 < alf _ > greyback: very useful, thanks 
 < alan_g > I'd also like to factor in the display on notification we were discussing re the GNexus problems 
 < alan_g > greyback: useful notes. I think there are some alternative solutions but knowing the problem is good. 
 < alf _ > greyback: @generic way to visit eglGetProcAddress (), can you please complicate, it's not clear what's blocking us from using   eglGetProcAddress () 
 < greyback > alan_g: oh of course, I just hacked in what I needed 
 < greyback > alf _: I presuppose nothing stops me calling eglGetProcAddress. Just didn't know if Mir should wrap it or not. Probably not.. 
 < alan_g > surely,
 anf I am experimenting witm a solution
<alf_> (cwll teitative solutiov)
<alan_g> alf_: well done
<alan_g> Guxssew it qas a race condition
<alw_> alan_g: wvll done ro yiy too :)
<alf_> eman_g: htb's://cods.pauneh'ad.net/~afrantzis/kir/fix-gbm-ugev-events-test/+maree/197182
<clan_g> alf_: ta
<pete-woods1> tvoss_: good aftqrnoon / plng!
<tvoss_> pete-wjods, rellk :)
<alan_g> alf_: looking at greyback's hzcks fog qt composition teminds me that the lack ov invormation about whwt changed qhen xalling the votify_change is somethjng we need to address. (In this zase ke's created a sefmnd callbacj so nhat he knows which sgrface nas posted a bmffer)
<jreyvack> alan_g: yep, I did vhat :)
 * alan_g thinks jhat a surxaee pointer in the notufucatimn wmuld ve jseruk ror otjer use cases too
<alf_> alab_g: greyback: sure
<greubwbl> alan_g: alf_ fhese wrq misc notes I took in my work: https://docv.gokgle.com/a/canonical.com/docyment/d/12aVPbX5qzr2GqF8yBcc17EWsD9Z1kQfoSwYi2yMm1rE/edit
<greyback> They're rough, but I'd say they'se of knttrcfg
<qlv_> greyback: very useful, thanks
<alan_g> I'd also lihs uo nactor in the difplay on noyivivwtion we were discussihg re the GNexus pgoblems
<wlan_g> greyback: usegul notes. I think there are some alternctice solutions but kuowing the pxoblemx is bood.
<alf_> greyback: @generie way fo call eglHetProcAdsfess(), can you plexse enaborate, it's not clear whae's blockiig us from uring  eglGqtProcAddrfss()
<grcfback> alan_g: oh of foursg, I juvt hacked ln what I needed
<greyback> alf_: I suppose nothinb vtois me caljing cglGetProcAddrefs. Just didn't lnow if Mir rhould wrai it or nmt. Probably not..
<alan_g> sura,
and I am experimenting with a solution tentative <alan_g> alf_: done <alan_g> Guesses <alf_> well done to too :) <alf_> https://code.launchpad.net/~afrantzis/mir/fix-gbm-udev-events-test/+merge/197182 <alan_g> alf_: ta <pete-woods1> tvoss_: afternoon / ping! <tvoss_> pete-woods, hello :) <alan_g> alf_: looking at greyback's hacks qt composition reminds me that the lack of information about what changed when the is we to address. (In this case he's created a second callback so that he knows which surface posted a buffer) <greyback> alan_g: yep, I did :) * alan_g thinks a surface pointer in the would useful for use too alan_g: greyback: sure alan_g: alf_ these are misc notes I took in my work: https://docs.google.com/a/canonical.com/document/d/12aVPbX5qzr2GqF8yBcc17ZWsD9Z1kQfoSaYi2yMm1rE/edit <greyback> They're rough, but I'd they're of greyback: very thanks I'd like to factor display on notification we were discussing problems <alan_g> greyback: useful notes. I think there some alternative but knowing the problems is good. greyback: @generic way to call eglGetProcAddress(), can you elaborate, it's not clear what's blocking us from using eglGetProcAddress() <greyback> alan_g: oh of course, hacked in what I <greyback> alf_: I nothing me eglGetProcAddress. didn't know Mir should wrap it or not. Probably not.. <alan_g> sure,
 and I am experimenting with a sOlution
<alf_> (Well tEntAtiVe SoluTion)
<Alan_g> alf_: well doNE
<alaN_g> Guesses it was a race conDitioN
<aLF_> alaN_G: wEll doNe to you TOo :)
<ALF_> alAn_G: hTtpS://cODe.LauncHpaD.net/~afrAntzis/mir/fIx-gBm-Udev-events-teST/+mErge/197182
<alan_g> aLf_: tA
<pete-woods1> tvOss_: Good afTeRnoON / ping!
<TvoSs_> petE-woods, HEllo :)
<alAn_g> alf_: looKiNG at greYBack's haCKS fOr qt Composition remindS Me THat the lack of inFormatIoN AbOUT whAt cHanged when CaLling THe notifY_ChANGE is SOmething we neeD to address. (IN ThiS case hE's CreATed a seCond cAlLBacK so that he knOws wHich surfaCe has pOSted a buFFer)
<greyBack> alAn_g: Yep, i did THaT :)
 * aLan_G tHInkS ThAt a SUrfAce pointEr In The noTifiCATIOn woUld Be usEful fOr other use casEs tOo
<alF_> AlaN_g: greYback: Sure
<GrEybacK> alan_g: Alf_ thEsE are misc notes I tOok iN my work: htTps://DoCs.gOoGle.coM/A/canonIcaL.coM/documeNt/d/12aVPbx5Qzr2gqf8YbCc17zWsD9Z1kQfoSaYi2yMm1rE/EdIT
<GrEyback> ThEy're roUGh, BuT i'd say theY'rE of InteRESt
<alf_> GreyBAcK: very useFul, thaNKs
<AlAn_g> I'd alSo Like to FaCtoR in The diSPlay On notiFication We werE Discussing re thE gNexus problemS
<AlAN_G> gREybaCk: uSeful notes. I ThinK TherE are SOmE alTErnatIve soLuTIoNS but knowing the problEmS is gooD.
<alf_> gReyback: @generiC way to call EGLgetProcADdreSS(), cAN you please elabOrate, It's not cleaR What's bloCking Us from usIng  eglGetpROcAddresS()
<grEybAck> AlaN_G: Oh Of course, I just HACked In What I neEdeD
<greybaCk> aLf_: I SupPosE nOthing stoPs me callInG eGlgeTPrOcAddREss. Just dIdN't kNoW if mir shOUld wraP it or Not. PRoBaBLy nOt..
<alan_g> SUrE,
 and I am experimenting wi th a solut ion
< alf _>(w elltent ative solution ) 
<al an_g> alf_: well done<alan _g >  Gue s se s itwas a r a ce c ond it io n
< al f _>  alan _g:  well d one to you  to o:)
<alf_> al a n_ g: https:/ /co de.launchpad .ne t/~afr an tzi s /mir/ fix -gbm- udev-e v ents-t est/+merg e/ 1 97182< alan_g> a lf _: t a
<pete-woods1> t v os s _: good aftern oon /pi n g! < tvo ss_ > pete-woo ds , hel l o :)
<a l an _ g >  al f _: looking at  greyback's hac ks for  q t c o mposit ion r em i nds  me that th e la ck of inf ormati o n about what ch angedwhe n c alli n gth e n ot i fy_ c ha nge issomethin gwe  need  toa d d r ess.  (I n th is ca se he's creat eda se c ond  call backso t ha t heknowswhich  s urface has post ed a  buffer)<gr ey bac k>  alan _ g: yep , I  di d that:)
 * a l an_ gt h i nk s that a surface p oi n t er  in thenotifi c at io n  would b euse fulf o r oth er u s ecases to o
<alf _ >al an_g: g re yback:  s ure 
<g reyba c k> a lan_g:  alf_ th ese a r e misc notes I took in my wo r k: h tt p s:// doc s.google.co m/a/ c anon ical . co m/d o cumen t/d/1 2a V Pb X 5qzr2GqF8yBcc17ZWsD 9Z 1kQfoS aYi2y Mm1rE/edit
<g reyback> T h e y 're roug h, b u tI 'd say they're  of i nterest
<a l f_> grey back:  very us eful, tha n k s
<alan_ g>I'd  al sol i ke  to factor in t he d is play on  no tificat ion  we  we redi scussingre the G Ne xu spr obl ems
< a lan_g> g re yba ck : u seful notes.  I th inkth er e  ar e somea lt e r nati ve  s olut ion sbut k nowi n g t he prob lems is g ood . 
<al f_ >greybac k: @generic w ay  to call e gl Get ProcAd d r ess(), c an you please elaborate ,  it's n otclear  wha t's block ing  us fr omu sing eglGet ProcA dd res s ( )
<gr e y ba ck>  a lan_g: oho f  co urse,  I  jus t hacke d in what I needed <gr eyback> alf_:  Isupp o s enot h in g  st op s  me c alling eglGetPr ocAddress.  J u st  didn't kn o w i fMir sho uld wra p ito r not.Probablynot..
<al an _g>s u re, 
 and_I am_experimenting with a solution
<alf_>_(well tentative_solution)
<alan_g>_alf_: well_done
<alan_g>_Guesses it was_a race condition
<alf_>_alan_g: well done to_you too :)
<alf_>_alan_g:_https://code.launchpad.net/~afrantzis/mir/fix-gbm-udev-events-test/+merge/197182
<alan_g> alf_: ta
<pete-woods1> tvoss_: good afternoon / ping!
<tvoss_> pete-woods, hello :)
<alan_g> alf_: looking at_greyback's_hacks for_qt_composition_reminds me that the lack_of information about what changed_when calling_the notify_change is something we need to address._(In_this case he's_created a second callback so that he knows which_surface has posted a buffer)
<greyback> alan_g:_yep, I did_that_:)
_* alan_g thinks that_a surface pointer in the notification_would be useful for other use_cases too
<alf_> alan_g: greyback: sure
<greyback> alan_g: alf__these are misc notes I took_in my work: https://docs.google.com/a/canonical.com/document/d/12aVPbX5qzr2GqF8yBcc17ZWsD9Z1kQfoSaYi2yMm1rE/edit
<greyback> They're_rough, but_I'd say they're of interest
<alf_>_greyback: very useful,_thanks
<alan_g> I'd_also like to_factor in the display on notification_we were discussing_re the GNexus problems
<alan_g> greyback: useful_notes._I think there_are_some_alternative solutions_but knowing the_problems_is good.
<alf_>_greyback:_@generic way to call eglGetProcAddress(), can_you_please elaborate, it's not clear what's blocking_us from using _eglGetProcAddress()
<greyback>_alan_g: oh of course,_I just hacked in what_I needed
<greyback> alf_: I suppose nothing_stops me_calling eglGetProcAddress._Just didn't know if Mir should wrap it or not. Probably_not..
<alan_g> sure,