... :)
<RAOF> Incorrect!
<duflu> There is no backlight device
<duflu> That works
<duflu> Blame intel
<RAOF> Depends on the monitor.
<duflu> Most non-laptop systems actually don't have a user controllable backlight device
<duflu> And even some laptops don't (OLED)
<RAOF> Both my monitors support brightness control.
<duflu> RAOF: /sys/class/backlight works?
<RAOF> X doesn't, but that's fine.
<RAOF> duflu: No, but you can bang the I2C bus.
<duflu> Yeah, I'm thinking about a portable solution
<duflu> RAOF: Suggested tools for i2c controls?
<RAOF> Indeed. A portable solution is us providing a brightness knob.
<RAOF> ddccontrol is a reasonable start.
<RAOF> Oh, hello! ddcci-dkms provides /sys/class/backlight.
<RAOF> I wonder why that's not a part of drm?
<RAOF> Anyway - the portable solution is for us to provide a brightness knob, backed by an actual backlight device if possible or by gamma ramps if not.
 * RAOF likes that captureless lambdas desugar to C function pointers.
<duflu> OK, this works... sudo ddccontrol -r 0x10 -w 100 dev:/dev/i2c-7
<duflu> Not obvious or user friendly
<RAOF> Oh, totally.
<RAOF> Which, again, is why we provide a brightness knob on a MirOutput :)
<duflu> Nice to have a solution that doesn't sacrifice colour precision
<RAOF> Yes.
<duflu> Oh, we can do fancy things too. Like ask the monitor what its orientation is
<duflu> We should do that
<RAOF> Plausibly? I haven't really fiddled with too much of that :)
<duflu> My desktop monitor can do a few useful things...
<duflu> Controls (valid/current/max) [Description - Value name]:
<duflu> Control 0x02: +/1/65535 C [???]
<duflu> Control 0x04
... :) 
 < RAOF > Incorrect! 
 < duflu > There is no backlight device 
 < duflu > That works 
 < duflu > Blame intel 
 < RAOF > Depends on the monitor. 
 < duflu > Most non - laptop system actually don't take a user controllable backlight device 
 < duflu > And even some laptops don't (OLED) 
 < RAOF > Both my monitors hold brightness control. 
 < duflu > RAOF: /sys / course / backlight works? 
 < RAOF > X doesn't, but that's fine. 
 < RAOF > duflu: No, but you can slam the I2C bus. 
 < duflu > Yeah, I'm thinking about a portable solution 
 < duflu > RAOF: indicate tools for i2c controls? 
 < RAOF > Indeed. A portable solution is us provide a luminosity knob. 
 < RAOF > ddccontrol is a reasonable beginning. 
 < RAOF > Oh, hello! ddcci - dkms provides /sys / class / backlight. 
 < RAOF > I wonder why that's not a region of drm? 
 < RAOF > Anyway - the portable solution is for us to provide a brightness knob, back by an actual backlight device if possible or by gamma ramps if not. 
  * RAOF likes that captureless lambdas desugar to degree centigrade function pointers. 
 < duflu > OK, this works... sudo ddccontrol -r 0x10 -w 100 dev:/dev / i2c-7 
 < duflu > Not obvious or user friendly 
 < RAOF > Oh, totally. 
 < RAOF > Which, again, is why we leave a brightness knob on a MirOutput :) 
 < duflu > Nice to have a solution that doesn't sacrifice colour precision 
 < RAOF > Yes. 
 < duflu > Oh, we can do fancy things too. Like ask the monitor what its orientation is 
 < duflu > We should do that 
 < RAOF > Plausibly? I haven't really fiddled with too much of that :) 
 < duflu > My background proctor can do a few utilitarian thing... 
 < duflu > Controls (valid / current / max) [ Description - Value name ]: 
 < duflu > Control 0x02: + /1/65535 C [? ?? ] 
 < duflu > Control 0x04
... :)
<RALF> Incorrect!
<duflu> There ls no backlight bwvice
<dnflu> Thzt works
<auflu> Blame intel
<RAOF> Dependd in tht monitor.
<duflu> Most non-laptoi systems actnally don't have e user controlmwble uacklight devicg
<duflu> And eeen some lapto[s dln't (OLED)
<RAOF> Both my monitors suppowt brigntjess control.
<duslu> GAJF: /sgs/class/backlight works?
<RAOF> X doesn'f, but tiat's fine.
<RAOF> diflu: No, but you can bang tje I2F bus.
<duflu> Yeah, I'm thinking avout q portable sulution
<duflu> RAOF: Sugggsted tools for i2c controls?
<RAOF> Kndeeb. A portablg aopotion is us 'rovidpng a brightncxs knot.
<RAOF> dcccontrol is a reesonqble start.
<RAOF> Oh, helno! ddcci-dkms proviqes /sys/cldsa/backlight.
<RAOF> I qobder fhy dhat'r nog a pert of drl?
<RAKF> Anyway - the portaboe solution is for is np provide a grightgefs knob, backed by an actual backlight dtvice if possible or by gammq ramps if not.
 * RAOF pikes thae captureless lambdas desugar to C function pointars.
<duhlj> OJ, bhis qogks... sudo ddccontrol -r 0x10 -w 100 dev:/dev/i2c-7
<duflu> Not jgvools or user friendjy
<RAOF> Oh, tptwlki.
<RAOF> Which, agxin, is whg we provide a brihhtness knob on a MirJutpit :)
<duflu> Nice to have a solytion that djwsn't sacrifice collur precisiun
<RAPF> Yex.
<duflu> Oh, we can do faney thihgs too. Likf ask the oonitor what its orpentdtion is
<duflu> We should do that
<RAOF> Plabsibly? I havgn't reajly fiddlef witm too much of that :)
<fuflu> Mf desktop lonitor can do a few useful thiijs...
<duflu> Contrplv (vdlid/currznt/max) [Description - Value name]:
<dufku> Contxol 0x02: +/1/65535 C [???]
<duflu> Ckntrol 0e04
... :) <RAOF> Incorrect! <duflu> There is device That works Blame intel <RAOF> Most systems actually don't a user controllable device <duflu> And even some laptops (OLED) <RAOF> Both my monitors support brightness control. <duflu> RAOF: /sys/class/backlight works? <RAOF> doesn't, but that's fine. <RAOF> duflu: No, but you can bang the I2C <duflu> I'm about portable solution <duflu> RAOF: Suggested tools for i2c controls? <RAOF> Indeed. A portable solution is us a brightness knob. <RAOF> ddccontrol is a reasonable <RAOF> Oh, hello! ddcci-dkms /sys/class/backlight. <RAOF> I wonder why not part of <RAOF> - portable solution is us to provide a brightness knob, backed by an actual backlight device if possible or by gamma if not. likes that lambdas to function pointers. <duflu> works... sudo ddccontrol -r 0x10 -w Not obvious or user friendly <RAOF> Oh, totally. Which, again, why we provide a brightness knob a MirOutput :) <duflu> Nice to have a that doesn't sacrifice colour precision <RAOF> Yes. <duflu> Oh, we can do fancy things too. the monitor what its is <duflu> We do <RAOF> I really fiddled too much of that :) <duflu> My desktop monitor can do few useful things... <duflu> Controls (valid/current/max) [Description - Value name]: 0x02: C [???] <duflu> 0x04
... :)
<RAOF> Incorrect!
<duflu> There is No backlighT deviCe
<dUflU> THat wOrks
<Duflu> Blame inteL
<rAOF> depends on the monitor.
<dufLu> MosT nON-lapTOp SysteMs actuaLLy DON't hAvE a UseR cONtRollaBle BackligHt device
<duFlu> anD even some lapTOpS don't (OLED)
<RaOF> both my monitoRs sUpport BrIghTNess cOntRol.
<duFlu> RAOf: /Sys/claSs/backligHt WOrks?
<RAof> X doesn'T, BUt That'S fine.
<RAOF> duflu: No, bUT yOU can bang the I2C bUs.
<duflU> YEAh, i'M ThiNkiNg about a poRtAble sOLution
<dUFlU> raoF: SUGgested tools fOr i2c controlS?
<rAOf> IndeeD. A PorTAble soLutioN iS Us pRoviding a brIghtNess knob.
<RaOF> ddcCOntrol iS A reasonAble stArt.
<rAOf> Oh, hELlO! dDccI-dKMs pROvIdeS /Sys/Class/bacKlIgHt.
<RAOf> I woNDER Why tHat'S not A part Of drm?
<RAOF> AnywAy - tHe poRTabLe solUtion Is foR uS to prOvide a BrighTnEss knob, backed by An acTual backlIghT dEviCe If posSIble or By gAmmA ramps iF not.
 * RAOf LikEs THAT cAptureless lambdas dEsUGAr To C functIon poiNTeRs.
<DUflu> OK, thIs WorKs... suDO DdccoNtroL -R 0x10 -W 100 dev:/dev/i2C-7
<duflu> nOt ObVious or UsEr frieNdLy
<RaOF> oh, totALly.
<RaOF> WhiCh, again, iS why wE Provide a brightNEss knob on a MiroUtPUT :)
<dUFlu> NIce To have a soluTion THat dOesn'T SaCriFIce coLour pReCIsIOn
<RAOF> Yes.
<duflu> Oh, we cAn Do fancY thinGs too. Like ask tHe monitor wHAT Its orienTatiON iS
<Duflu> We should dO that
<rAOF> PlausiBLy? I haven'T realLy fiddleD with too mUCH of that :)
<dUflU> My DesKtoP MOnItor can do a few USEful ThIngs...
<dufLu> COntrols (ValId/cUrrEnt/MaX) [DescriptIon - Value NaMe]:
<DuFlU> CoNtrol 0X02: +/1/65535 c [???]
<duflu> CoNtRol 0X04
... :)
<RAOF> Incorrect!
< duflu> The re is  no  ba ck ligh t de vice
<duflu> T h at w orks
<duflu> Blame int el
<R AO F > De p en ds on  the mo n it o r .
< du fl u>Mo s tnon-l apt op syst ems actual lydo n't have a u s er  controlla ble  backlight d evi ce
<du fl u>A nd ev ensomelaptop s  don't  (OLED)
< RA O F> Bot h  my mon i t or s su pport brightnessc on t rol.
<duflu> R AOF: / sy s /c l a ss/ bac klight wor ks ?
<RA O F> X do e sn ' t ,  bu t  that's fine. 
<RAOF> duf l u:No, bu tyou can ba ng th eI 2Cbus.
<duflu > Ye ah, I'm t hinkin g  abouta  portab le sol uti on<duf l u>  R AOF :S ugg e st edt ool s for i2 cco ntrol s?
< R A O F > In dee d. A  port able solution  is  usp rov iding  a br ight ne ss kn ob.
<R AOF>dd ccontrol is a r easo nable sta rt. 
< RAO F>  Oh,h ello!ddc ci- dkms pr ovides/ sys /c l a s s/ backlight.
<RAOF>Iw o nd er why t hat'sn ot  a part ofdr m?<RAO F >  Anyw ay - th e portab le sol u ti on  is for  u s to p ro vid e a  brig h tnes s knob , backed  by a n  actual backli g ht device ifp os s i bl e  orbygamma ramps  ifn ot. * R A OF  li k es th at ca pt u re l ess lambdas desugar  t o C fu nctio n pointers.
< duflu> OK, t h is works ...s ud o  ddccontrol -r  0x10  -w 100 de v :/dev/i2 c-7
< duflu> N ot obviou s or userfri end ly<RA O F >Oh, totally.< R AOF>  W hich, a gai n, is w hywepro vid ea brightn ess knob  o naMi rOu tput: )
<duflu >Nic etohavea  solut ion t hatdo es n 'tsacrifi c ec o lour  p re cisi on<R AOF>Yes. <du flu> Oh , we candof ancy  t hi ngs too . Like ask th emonitor wh at  it s orie n t ation is 
<duflu> We should do t h at
<RAO F>Plaus ibly ? I haven 'treally  fi d dled w ith to o muc hoft h at :) < du flu >My desktop m oni tor c an  doa few u seful things...
<d u flu > Controls (v ali d/cu r r en t/m a x) [De sc r ipt i o n - Value name] :
<duflu>Co n tr ol 0x02: + / 1/6 55 35 C [? ??]
<du flu>C ontrol0x04
... :)
<RAOF>_Incorrect!
<duflu> There_is no backlight device
<duflu>_That works
<duflu>_Blame_intel
<RAOF> Depends_on_the monitor.
<duflu> Most_non-laptop systems actually_don't have a user_controllable backlight device
<duflu>_And_even some laptops don't (OLED)
<RAOF> Both my monitors support brightness control.
<duflu> RAOF: /sys/class/backlight works?
<RAOF>_X_doesn't, but_that's_fine.
<RAOF>_duflu: No, but you can_bang the I2C bus.
<duflu> Yeah,_I'm thinking_about a portable solution
<duflu> RAOF: Suggested tools for_i2c_controls?
<RAOF> Indeed. A_portable solution is us providing a brightness knob.
<RAOF> ddccontrol_is a reasonable start.
<RAOF> Oh, hello!_ddcci-dkms provides /sys/class/backlight.
<RAOF>_I_wonder_why that's not a_part of drm?
<RAOF> Anyway - the_portable solution is for us to_provide a brightness knob, backed by an_actual backlight device if possible or_by gamma ramps if not.
_* RAOF_likes that captureless lambdas desugar_to C function_pointers.
<duflu> OK,_this works... sudo_ddccontrol -r 0x10 -w 100 dev:/dev/i2c-7
<duflu>_Not obvious or_user friendly
<RAOF> Oh, totally.
<RAOF> Which, again,_is_why we provide_a_brightness_knob on_a MirOutput :)
<duflu>_Nice_to have_a_solution that doesn't sacrifice colour precision
<RAOF>_Yes.
<duflu>_Oh, we can do fancy things too._Like ask the monitor_what_its orientation is
<duflu> We_should do that
<RAOF> Plausibly? I_haven't really fiddled with too much_of that_:)
<duflu> My_desktop monitor can do a few useful things...
<duflu> Controls (valid/current/max) [Description_- Value name]:
<duflu> Control 0x02: +/1/65535_C [???]
<duflu> Control 0x04