00:44.48 | *** join/#maemo-ssu freemangordon_ (~freemango@46.249.74.23) |
01:30.11 | *** join/#maemo-ssu aap (~drew@cpe-174-101-232-161.cinci.res.rr.com) |
02:28.17 | *** join/#maemo-ssu aap (~drew@cpe-174-101-232-161.cinci.res.rr.com) |
03:31.37 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
04:20.47 | DocScrutinizer05 | in filter-brightness-als.h there's this structure: |
04:20.53 | DocScrutinizer05 | { |
04:20.54 | DocScrutinizer05 | { |
04:20.56 | DocScrutinizer05 | { 32, 64 }, |
04:20.57 | DocScrutinizer05 | { 100, 1000 }, |
04:20.59 | DocScrutinizer05 | { -1, -1 }, |
04:21.03 | DocScrutinizer05 | }, { 5, 5, 0, 0, 0, 0 } |
04:21.05 | DocScrutinizer05 | } |
04:22.04 | DocScrutinizer05 | it means indicator LED will work on 5(% brightness?) up til 64LUX, and on 5 up till 1000LUX, above 1000 it switches to 0. |
04:22.42 | DocScrutinizer05 | could somebody please patch { 5, 5, 0, 0, 0, 0 } to { 5, 5, 5, 5, 5, 0 } ? |
04:23.34 | DocScrutinizer05 | or just { 5, 5, 5, 0, 0, 0 } |
04:25.49 | DocScrutinizer05 | one char patch ;-) |
04:26.00 | DocScrutinizer05 | my favourite typ eof patches |
04:26.29 | DocScrutinizer05 | it's definitely a typo |
04:29.41 | DocScrutinizer05 | btw we also see that this annoying blanking of indicator LED in bright daylight only happens when brightness profile is set to MAX (aka "5") |
04:31.07 | DocScrutinizer05 | when you reduce "screen" brightness to anything <MAX/5, some of the former unflawed LED brightness profiles from als_profile_struct led_als_profiles_rx51[] gets used |
04:32.29 | DocScrutinizer05 | each of the other 4 profiles has N+1 values for N LUX-limit tuples |
04:33.58 | DocScrutinizer05 | ooops actually not |
04:34.36 | DocScrutinizer05 | it's totally confusing, it seems like only profile#3 is defined at all |
04:34.58 | DocScrutinizer05 | 1,2,4,5 are all all zeroes |
04:36.01 | DocScrutinizer05 | I skipped a whole page in that struct desert, sorry |
04:36.51 | DocScrutinizer05 | here you are: http://privatepaste.com/33cb0318d8 |
04:37.54 | DocScrutinizer05 | while a proer definition like something like http://privatepaste.com/aada1e8273 |
04:38.02 | DocScrutinizer05 | proper* |
04:38.15 | DocScrutinizer05 | looks* dang |
04:56.23 | DocScrutinizer05 | honestly WTF?! http://privatepaste.com/048a9fe57d |
05:53.16 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@183.32.203.89) |
06:12.57 | DocScrutinizer05 | the structure starts in libfilter-brightness-als.so at 0x85f8 |
06:15.02 | DocScrutinizer05 | thr byte to patch from 0x00 to 0x05 is at 0x86a8 |
07:18.15 | *** join/#maemo-ssu unclouded (~neil@2001:4428:200:80fc:7e05:7ff:fe0d:d421) |
07:22.24 | *** join/#maemo-ssu sixwheeledbeast (~paul@cl-1547.lon-02.gb.sixxs.net) |
07:54.32 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-80-71.residential.rdsnet.ro) |
08:00.07 | *** join/#maemo-ssu LauRoman|Alt (~LauRoman@5-14-80-71.residential.rdsnet.ro) |
08:15.46 | *** join/#maemo-ssu freemangordon (~freemango@46.249.74.23) |
08:49.12 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
08:59.50 | *** join/#maemo-ssu NIN101 (~NIN@p5DD2BE2F.dip0.t-ipconnect.de) |
09:01.02 | *** join/#maemo-ssu _rd (~rd@p5088FDAB.dip0.t-ipconnect.de) |
09:08.53 | *** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm) |
09:59.25 | *** join/#maemo-ssu NIN101 (~NIN@p5DD2BE2F.dip0.t-ipconnect.de) |
10:14.40 | *** join/#maemo-ssu Woody14619 (~Woody1461@Maemo/community/contributor/Woody14619) |
10:38.42 | *** join/#maemo-ssu _rd (~rd@p5088FDAB.dip0.t-ipconnect.de) |
10:47.33 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
11:06.52 | *** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl) |
11:21.33 | *** join/#maemo-ssu _rd (~rd@p5088FDAB.dip0.t-ipconnect.de) |
12:39.47 | *** join/#maemo-ssu _rd (~rd@p5088FDAB.dip0.t-ipconnect.de) |
12:53.55 | *** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1) |
13:02.39 | *** join/#maemo-ssu okias (~okias@berger.cust.centro-net.cz) |
13:15.09 | *** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm) |
15:00.25 | *** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1) |
15:00.27 | *** join/#maemo-ssu M13 (~MirandaLS@170.133-224-87.telenet.ru) |
15:17.35 | *** join/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
15:35.05 | DocScrutinizer05 | freemangordon: seen the above? |
15:35.31 | freemangordon | DocScrutinizer05: hmm? which one? |
15:35.47 | DocScrutinizer05 | the previous ~40 lines |
15:36.02 | freemangordon | just saw them |
15:36.10 | freemangordon | I read on TMO |
15:36.17 | DocScrutinizer05 | ooh, thanks |
15:36.37 | freemangordon | DocScrutinizer05: I'll patch mce in cssu, this patch is a nobrainer |
15:36.46 | DocScrutinizer05 | yes |
15:37.05 | freemangordon | but I'll need jonwil, there is a report of some problem with mce |
15:37.13 | DocScrutinizer05 | o.O |
15:37.28 | freemangordon | http://talk.maemo.org/showpost.php?p=1387420&postcount=34 |
15:38.01 | freemangordon | sounds weird, but still |
15:39.00 | DocScrutinizer05 | :-/ |
15:39.08 | DocScrutinizer05 | confirm it? |
15:39.44 | DocScrutinizer05 | I mean, the description is clear enough to either reproduce or reject as invalid? |
15:40.16 | freemangordon | sure, that is why I wait for jonwil to appear, my confirmation without a fix is useless |
15:40.24 | freemangordon | I guess it is not invalid |
15:40.31 | freemangordon | (the report) |
15:41.05 | freemangordon | is going to check the stck behaviour |
15:41.09 | freemangordon | *stock |
15:44.53 | freemangordon | yep, with stock mce pushing a button after the display was dimmed on timeout, unlocks it |
15:48.05 | DocScrutinizer05 | please elaborate |
15:48.41 | freemangordon | open the keyboard, let the screen to dim and press a button on the keyboard |
15:48.52 | DocScrutinizer05 | yes, unlocks screen |
15:49.20 | DocScrutinizer05 | even qualifier keys like shift do |
15:49.25 | freemangordon | not on mce replacement it seems: |
15:49.28 | DocScrutinizer05 | and the keypress gets eaten |
15:49.35 | freemangordon | "... the keyboard gets locked and can only be unlocked when touching the display" |
15:50.30 | DocScrutinizer05 | this btw works in both states: dim and blank display |
15:50.45 | freemangordon | :nod: |
15:51.03 | DocScrutinizer05 | in dim it has a setting "lock on dim" or sth like that, in mce.ini, IIRC |
15:51.27 | DocScrutinizer05 | I may be mistaken on that though |
15:51.36 | DocScrutinizer05 | it doesn't make sense |
15:51.52 | DocScrutinizer05 | checks mce.ini |
15:55.17 | DocScrutinizer05 | # Policy for keypad interrupts |
15:55.19 | DocScrutinizer05 | # |
15:55.20 | DocScrutinizer05 | # 2 - leave keypad interrupts on even after blanking |
15:55.22 | DocScrutinizer05 | # (used to support pass-through of +/-) |
15:55.23 | DocScrutinizer05 | # 1 - disable interrupts immediately |
15:55.25 | DocScrutinizer05 | # 0 to wait until display is blanked |
15:55.26 | DocScrutinizer05 | DisableKPImmediately=1 |
16:02.06 | DocScrutinizer05 | freemangordon: I have quite a number of patches for mce, for sanitizing the ill-conceived LP5523 handling. Starting with freeing up engine 3 from that idiotic exclusive task of 100ms kbd backlight ramping, and continuing with an augmented syntax for pattern definitions, and of course also allowing to exploit full program memory available in LP5523 which is twice the size of what mce (and the kernel driver) supports |
16:03.14 | freemangordon | DocScrutinizer05: sorry, preparing new -thumb update right now, cannot share time for mce :) |
16:03.29 | DocScrutinizer05 | no problem, I'll provide patches |
16:04.10 | DocScrutinizer05 | also for lp5523.ko |
16:04.52 | DocScrutinizer05 | rGB *pfff* |
16:05.15 | DocScrutinizer05 | 122 maybe |
16:05.46 | DocScrutinizer05 | # "r", "g", "b" maps the LED to engine 1 |
16:05.47 | DocScrutinizer05 | # "R", "G", "B" maps the LED to engine 2 |
16:05.49 | DocScrutinizer05 | # Example: |
16:05.50 | DocScrutinizer05 | # "rG" maps the red LED to engine 1, |
16:05.52 | DocScrutinizer05 | # the green LED to engine 2, |
16:07.29 | DocScrutinizer05 | the nice part is a "312" (for R=engine3, G=engine1, B=2) is compatible with that "rGb" scheme |
16:10.11 | DocScrutinizer05 | and of course extending pattern length is a nobrainer, as is appending pattern for engine3 |
17:15.05 | *** join/#maemo-ssu thedead1440_ (~thedead14@unaffiliated/thedead1440) |
17:15.44 | *** join/#maemo-ssu xes (~xes@unaffiliated/xes) |
17:18.36 | *** join/#maemo-ssu thedead1440_ (~thedead14@unaffiliated/thedead1440) |
17:37.32 | *** join/#maemo-ssu _rd (~rd@p5088FDAB.dip0.t-ipconnect.de) |
18:01.09 | DocScrutinizer05 | freemangordon: hey guy, you're still alive? |
18:01.57 | DocScrutinizer05 | not that we were in a particular hurry to fix a autobuilder lockup that's already lingering since 4 days |
18:02.06 | DocScrutinizer05 | ;-) |
18:03.38 | DocScrutinizer05 | also would be highly appreciated when you /join the admin channel |
18:19.00 | kerio | DocScrutinizer05: aww, that patch will make the modified filter-brightness-als obsolete |
18:19.07 | kerio | and i don't know if the dude who made it is still around |
18:20.38 | DocScrutinizer05 | kerio: hmm? |
18:21.50 | DocScrutinizer05 | kerio: which patch? why does it make anything obsolete? |
18:22.31 | DocScrutinizer05 | and what? |
18:22.48 | kerio | filter-brightness-als.so |
18:22.54 | kerio | one of the mce thingies |
18:23.20 | DocScrutinizer05 | yes, that's the one where you need to patch one byte to fix the indicatior LED |
18:23.44 | kerio | it's one byte in C |
18:23.51 | kerio | who knows how many bytes it will be when compiled |
18:23.57 | kerio | maybe everything changes |
18:24.05 | DocScrutinizer05 | http://talk.maemo.org/showthread.php?t=91849 |
18:24.16 | kerio | yay |
18:25.06 | DocScrutinizer05 | and yes, I should clearly state which binary this instructions apply to |
19:00.21 | Pali | DocScrutinizer05: you have patches for kernel driver lp5523.ko? |
19:05.31 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
19:24.05 | DocScrutinizer05 | Pali: yep, though nothing tested for even compiling without flaws |
19:24.35 | DocScrutinizer05 | Pali: didn't come around to setting up a buld environment |
19:24.39 | Pali | DocScrutinizer05: if you want patch to be included in kp53, post it to kp TMO thread |
19:25.09 | Pali | or send me it or upload it |
19:25.24 | DocScrutinizer05 | sure, will do as soon as I can check anything for at least syntactical correctness |
19:25.30 | Pali | just I need to know if to wait for patch or relese version without it |
19:25.33 | Pali | ok |
19:27.34 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
19:30.45 | *** join/#maemo-ssu arcean (~arcean@aaeq229.neoplus.adsl.tpnet.pl) |
19:39.17 | *** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
19:42.04 | DocScrutinizer05 | don't wait |
19:42.47 | DocScrutinizer05 | it's not even in any state to consider publishing anything yet - maybe except for the API extension specs |
19:56.26 | DocScrutinizer05 | kerio: I still fail to see why my "patch" obsoletes anything |
19:56.45 | kerio | well apparently your patch is a hex edit too |
19:57.12 | DocScrutinizer05 | so? |
19:57.17 | kerio | so it's false |
19:57.29 | DocScrutinizer05 | *shrug* |
19:57.44 | DocScrutinizer05 | CBA to argue about that |
19:58.05 | kerio | my fear was that if it was a patch that needed a recompile |
19:58.15 | kerio | then the previous hex editing would require more finesse to be applied again |
19:58.46 | DocScrutinizer05 | so? |
19:59.03 | DocScrutinizer05 | I still don't see what's wrong with my patch |
19:59.11 | kerio | there's nothing wrong |
19:59.15 | kerio | it's actually much better |
20:48.39 | Pali | freemangordon: ping |
20:50.27 | Pali | freemangordon: new version of qt4-x11 and hildon-desktop is in git, but not in cssu-devel |
20:50.59 | Pali | same for status-area-orientationlock-applet |
20:51.01 | *** join/#maemo-ssu _rd (~rd@p5088FDAB.dip0.t-ipconnect.de) |
20:52.37 | Pali | going to build status-area-orientationlock-applet and push it to cssu-devel |
20:53.27 | Pali | done |
21:40.14 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-80-71.residential.rdsnet.ro) |
22:02.42 | freemangordon | Pali: I've fixed h-d today, will push it in -devel tomorrow |
22:02.51 | Pali | ok |
22:03.14 | freemangordon | Pali: is there something fixed in qt? |
22:03.36 | Pali | yes, because in git is newer version as in cssu-devel |
22:04.14 | freemangordon | Pali: any clue what is fized? |
22:04.17 | freemangordon | *fized |
22:04.20 | freemangordon | shit |
22:04.22 | freemangordon | FIXED |
22:04.26 | Pali | do not know |
22:04.38 | freemangordon | hmm, ok, will check |
23:02.03 | *** join/#maemo-ssu LauRoman|Alt (~LauRoman@5-14-86-200.residential.rdsnet.ro) |