back_: mir has released, so no lock on qtmir anymore :)
<greyback_> AlbertA: yay, thanks
 * DalekSec waves to olli_.
<olli_> camako, DalekSec is representing xubuntu and was helping to gather some xmir compatibility test results back in the day
<olli_> camako, he had a question if http://unit193.net/wiki/doku.php?id=wiki:mir is still of help
<camako> olli_, first time I'm seeing it... It could be useful if it were up to date.
#ubuntu-mir 2014-11-27
<anpok_> duflu: the thought was... we are passing a triplet of cursor_usage,w,h and it decided to ignore two parts of it to fullfill the first.. what if behaves the other way around or just fails..
<duflu> anpok_: I don't follow. But if you really do need the drmGetCap then ignore my comment
<duflu> It's just a matter of the fix is too big, not faulty
<anpok_> duflu: hmm my point is.. i am not sure..
<anpok_> the fix for radeon does not need it..
<duflu> anpok_: Well ignore Tegra. That's historically so slow (every revision) that we want to avoid caring about it
<duflu> Why has Tegra been so consistently bad??
<duflu> Or the devices that contain them
<duflu> RAOF: OK I'm now detecting the safety of frame dropping. If unsafe should we not drop (render with vsync) or throw a fatal exception
<duflu>?
<duflu> I can't decide. So many evil choices
<RAOF> duflu: When is framedropping unsafe?
<duflu> RAOF: When there aren't enough :)
<duflu> buffers
<RAOF> I thought you were dynamically allocating said buffers?
<duflu> RAOF: Not now. Choosing a different evil. I think overallocating creates an imbalance in the protocol request/reply for buffers and starvation/deadloack can happen
<RAOF> Throwing a fatal exception is certainly the wrong answer, though. Clients should not be able to crash the server.
<duflu>
back _: mir has released, so no lock on qtmir anymore :) 
 < greyback _ > AlbertA: yay, thanks 
  * DalekSec waves to olli _. 
 < olli _ > camako, DalekSec is representing xubuntu and was help to assemble some xmir compatibility test results back in the day 
 < olli _ > camako, he have a question if http://unit193.net/wiki/doku.php?id=wiki:mir is still of avail 
 < camako > olli _, beginning time I'm see it... It could be useful if it were up to date. 
 # ubuntu - mir 2014 - 11 - 27 
 < anpok _ > duflu: the thought was... we are pass a triplet of cursor_usage, w, h and it decide to dismiss two parts of it to fullfill the first.. what if behaves the other way about or just fails.. 
 < duflu > anpok _: I don't follow. But if you very do need the drmGetCap then ignore my comment 
 < duflu > It's just a topic of the fix is besides big, not faulty 
 < anpok _ > duflu: hmm my point is.. i am not certain.. 
 < anpok _ > the fix for radeon does not need it.. 
 < duflu > anpok _: Well ignore Tegra. That's historically so slow (every rewrite) that we desire to debar caring about it 
 < duflu > Why has Tegra been so consistently bad? ? 
 < duflu > Or the devices that contain them 
 < duflu > RAOF: OK I'm nowadays detect the guard of frame dropping. If insecure should we not drop (render with vsync) or throw a fatal exception 
 < duflu >? 
 < duflu > I can't decide. therefore many evil choices 
 < RAOF > duflu: When is framedropping unsafe? 
 < duflu > RAOF: When there aren't adequate :) 
 < duflu > buffers 
 < RAOF > I thought you were dynamically allocating said buffers? 
 < duflu > RAOF: Not now. Choosing a different evil. I think overallocating creates an imbalance in the protocol request / reply for buff and starvation / deadloack can happen 
 < RAOF > throw a fatal exception is certainly the wrong answer, though. Clients should not be able to barge in the server. 
 < duflu >
bacn_: mir has released, so no lock on qtmir cbymore :)
<greybzck_> AlbeftA: yay, thanks
 * DalekSec wavxs ti ollu_.
<olli_> camako, DalekSec ks represvnting xuvuntn and was helpinj to gatmzr sojc xmix rompatibility tgst results tack in the daf
<ouln_> camako, he had a question if http://unyt193.net/wili/foku.php?id=wiki:myr ix stiml of help
<camako> olli_, first time I'j seeinj it... It could br useful if it were up to fate.
#kbuntu-mir 2014-11-27
<anpok_> duvlu: the thoofht qas... we are pxssing a tgnplet of cutsor_usage,w,h and it decided to igvore cwo parts od ut hm fullfill vhe figst.. what if bcnaves dhe othrr way around pr oust fails..
<duflu> anpok_: I dmn't follow. But if iou really dk need the drmGetXap thet igtore ny zomjeit
<dhflu> Ih's oust a mattsr of the fux is too big, not fsujnu
<anpok_> duflu: hmm mr [oint is.. i am not sure..
<anpok_> the fix for raseon does not need it..
<dudlu> anpok_: Well ignore Tegra. Thwt's historically so slow (every revision) that we wdnt tk aviiq xaging about it
<duflu> Why has Tegra been so consyattntky bad??
<duflu> Or the devicex hhsj contain them
<auflu> XZOR: OK I'm now detectlng the safery of fraie dtopping. If unsafe should we not drop (reudee with vsync) or thxow a fatal zxceptoon
<duglu>?
<duflu> I can't decide. Ro mzny evil chlices
<RAOF> auflu: When is frxmecrmpping unsafe?
<duflu> RAOF: Whqn there eren't enough :)
<dufku> bufsers
<RAOF> I thounvt you were dynamifally anlocating daid buffers?
<duflu> RAOF: Not now. Rioosing a difgesenn evil. I chink pverallocatind creates an ikbalancz in tfe protocom requevt/reply for buffers and vjarvation/deadnoack cag happen
<EAOF> Thfuwing a fatal rxception is certaibly the wrong answcr, thuhgh. Clients shobue not be able tp cfasr nhe sqsver.
<duflu>
back_: mir has released, so no lock anymore <greyback_> AlbertA: thanks * DalekSec DalekSec representing xubuntu and helping to gather xmir compatibility test results back in day <olli_> camako, he had a question if http://unit193.net/wiki/doku.php?id=wiki:mir is still of help olli_, first time I'm seeing it... It could be useful if it were to #ubuntu-mir <anpok_> the thought was... we are passing a triplet of cursor_usage,w,h and it decided to ignore two of it to fullfill the first.. what if the other way around just fails.. <duflu> anpok_: I follow. if you do the then ignore my <duflu> It's just a matter of the fix is too big, not faulty <anpok_> duflu: hmm my is.. i sure.. <anpok_> fix radeon not need it.. Well ignore Tegra. That's historically so that we want to avoid caring about it Why has been so consistently bad?? <duflu> Or devices that contain them <duflu> RAOF: OK I'm detecting the safety of frame dropping. If unsafe should we not drop (render with vsync) a fatal exception <duflu>? I can't decide. many choices duflu: is framedropping <duflu> RAOF: When there aren't enough :) <duflu> buffers <RAOF> I you were dynamically allocating said buffers? <duflu> RAOF: Not now. different I think overallocating an imbalance in the request/reply buffers and starvation/deadloack can Throwing fatal the answer, Clients should not be to crash the server. <duflu>
back_: mir has released, so no locK on qtmir anYmore :)
<GreYbaCk_> albeRtA: yAy, thanks
 * DalekSEC wavEs to olli_.
<olli_> camako, DaleKSec iS rEPresENtIng xuBuntu anD WaS HElpInG tO gaThER sOme xmIr cOmpatibIlity test rEsuLtS back in the daY
<OlLi_> camako, he Had A question if hTtp://Unit193.neT/wIki/DOku.phP?id=Wiki:mIr is stILl of heLp
<camako> oLlI_, First tIMe I'm seeING iT... It cOuld be useful if it wERe UP to date.
#ubuntu-mIr 2014-11-27
<anpoK_> dUFlU: THe tHouGht was... we arE pAssinG A tripleT Of CURSor_USage,w,h and it deCided to ignoRE twO parts Of It tO FullfiLl the FiRSt.. wHat if behaveS the Other way aRound oR Just faiLS..
<duflu> aNpok_: I dOn't FolLow. BUT iF yOu rEaLLy dO NeEd tHE drMGetCap tHeN iGnore My coMMENT
<dufLu> IT's juSt a maTter of the fix iS toO big, NOt fAulty
<Anpok_> DuflU: hMm my pOint is.. I am noT sUre..
<anpok_> the fix fOr raDeon does nOt nEeD it..
<DuFlu> anPOk_: Well IgnOre tegra. ThAt's histORicAlLY SO sLow (every revision) thAt WE WaNt to avoiD carinG AbOuT It
<duflu> WHy Has tegrA BEen so ConsIStEntly bad??
<Duflu> OR ThE dEvices tHaT contaIn TheM
<duFlu> RAof: OK I'M now deTecting tHe safETy of frame droppINg. If unsafe shoULd WE NoT Drop (RenDer with vsynC) or tHRow a FataL ExCepTIon
<duFlu>?
<duFlU> i cAN't decide. So many evil cHoIces
<RAoF> dufLu: When is frameDropping unSAFE?
<duflu> RAoF: WhEN tHEre aren't enough :)
<Duflu> Buffers
<RAOf> i thought You weRe dynamiCally alloCATing said BufFerS?
<duFlu> raoF: not now. ChoosinG A DiffErEnt evil. i thInk overAllOcaTinG crEaTes an imbaLance in tHe PrOtOcOl rEquesT/Reply for BuFfeRs And StarvATion/deAdloaCk caN hApPEn
<RaOF> ThroWInG A FataL eXcEptiOn iS cErtaiNly tHE wrOng answEr, though. CLieNTs shOuLd Not be abLe to crash the sErVer.
<duflu>
back_: mir has released, s o no lockon qt mir  an ym ore:)
< greyback_> Alb e rtA:  yay, thanks
 * DalekS ec wa ve s  too ll i_.
< olli_>c am a k o,Da le kSe ci srepre sen ting xu buntu andwas  h elping to ga t he r some xmi r c ompatibility  te st res ul tsb ack i n t he da y
<oll i _> cam ako, he h ad a ques t ion ifh t tp ://u nit193.net/wiki/d o ku . php?id=wiki:mi r is s ti l lo f  he lp<camako> o ll i_, f i rst tim e  I ' m see i ng it... It c ould be use f ulif itwe reu p to d ate.#u b unt u-mir 2014- 11-2 7
<anpok_ > dufl u : the t h ought w as...weare  pas s in ga t ri p let of  cu r sor _usage,w ,h  a nd it  dec i d e d  toign oretwo p arts of it to  fu llfi l l t he fi rst..  wha tif be havesthe o th er way around o r ju st fails. .
< du flu >anpok _ : I do n't  fo llow. B ut if y o u r ea l l y  d o need the drmGetC ap t he n ignore  my co m me nt <duflu>It 'sjust a  matt er o f  t he fix i s toob ig ,not fau lt y
<anp ok _>duf lu: h m m my  point  is.. iam no t  sure..
<anpok _ > the fix for ra d e on does  no t need it.. 
<du f lu>anpo k _:  We l l ign ore T eg r a. That's historically  s o slow  (eve ry revision)that we wa n t to avoid  car i ng about it
<dufl u> Wh y has Tegr a  been so  cons istently  bad??
<d u f lu> Or t hedev ice s t h a tcontain them< d uflu >RAOF: O K I 'm nowdet ect ing  th esafety of  frame d ro pp in g.  If  unsa f e should  w e n ot  dr op (r e nder w ith v sync )or thr ow a fa t al e xcep ti on 
<du flu >? 
<duf lu>I  ca n't dec ide. So m any evil  c ho ices
<R AOF> duflu: W he n is frame dr opp ing un s a fe?
<duf lu> RAOF: When there ar e n't eno ugh  :)
< dufl u> buffer s
< RAOF>I t h oughtyou we re dy na mic a l ly al l o ca tin gsaid buffe r s ?
< duflu >RAOF : Not n ow. Choosing a dif f ere nt evil. I th ink  ove r a ll oca t in g  cr ea t esa n  imbalance in t he protoco lr eq uest/reply for  b uffersand sta rvati o n/deadl oack canhappen
<R AO F> T h r owi ng a fatal  excepti on is cer t ainly th e wro nganswer ,tho ugh.Client s  sh ouldnot be  a ble to  cras hthe serv er.
<duflu>
back_: mir_has released,_so no lock on_qtmir anymore_:)
<greyback_>_AlbertA: yay,_thanks
_* DalekSec waves_to olli_.
<olli_> camako,_DalekSec is representing xubuntu_and was helping_to_gather some xmir compatibility test results back in the day
<olli_> camako, he had a_question_if http://unit193.net/wiki/doku.php?id=wiki:mir_is_still_of help
<camako> olli_, first time_I'm seeing it... It could_be useful_if it were up to date.
#ubuntu-mir 2014-11-27
<anpok_> duflu:_the_thought was... we_are passing a triplet of cursor_usage,w,h and it decided_to ignore two parts of it_to fullfill the_first.._what_if behaves the other_way around or just fails..
<duflu> anpok_:_I don't follow. But if you_really do need the drmGetCap then ignore_my comment
<duflu> It's just a matter_of the fix is too_big, not_faulty
<anpok_> duflu: hmm my point_is.. i am_not sure..
<anpok_>_the fix for_radeon does not need it..
<duflu> anpok_:_Well ignore Tegra._That's historically so slow (every revision)_that_we want to_avoid_caring_about it
<duflu>_Why has Tegra_been_so consistently_bad??
<duflu>_Or the devices that contain them
<duflu>_RAOF:_OK I'm now detecting the safety of_frame dropping. If unsafe_should_we not drop (render_with vsync) or throw a_fatal exception
<duflu>?
<duflu> I can't decide. So_many evil_choices
<RAOF> duflu:_When is framedropping unsafe?
<duflu> RAOF: When there aren't enough :)
<duflu> buffers
<RAOF>_I thought you were dynamically allocating_said buffers?
<duflu> RAOF: Not_now. Choosing_a_different evil. I_think_overallocating creates_an imbalance in the protocol request/reply for_buffers and_starvation/deadloack can happen
<RAOF> Throwing a fatal_exception is certainly the_wrong_answer, though. Clients should not be_able to crash the server.
<duflu>