--- Log for 29.07.113 Server: pratchett.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 3 days and 5 hours ago 00.01.25 Quit Rower (Quit: Hmmm...) 00.03.01 Quit bertrik (Ping timeout: 240 seconds) 00.04.33 Quit lorenzo92 (Remote host closed the connection) 00.10.26 Quit pamaury (Ping timeout: 276 seconds) 00.10.43 Quit stripwax (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 00.13.09 # saratoga: iPod Classic codec performance, unboosted: http://pastebin.com/egfp91EF 00.19.10 *** Saving seen data "./dancer.seen" 00.23.32 Quit lebellium (Quit: ChatZilla 0.9.90.1 [Firefox 23.0/20130725195523]) 00.31.26 Quit ender` (Quit: Eighty percent of all people consider themselves to be above-average drivers.) 00.35.24 Quit tchan (Quit: WeeChat 0.4.1) 01.08.51 # saratoga: Fuze+ codec performance, unboosted: http://pastebin.com/hKT6LWrG 01.11.00 # good night 01.11.11 # <[Saint]> Huzzah. Some real results. 01.11.13 # <[Saint]> Nice. 01.12.25 # <[Saint]> Unboosted results are a lot nicer when the targets in question very rarely, if ever, need to boost under normal circumstances. 01.13.06 # <[Saint]> ...though I'm pretty sure the Classic inherits the iPod/clickwheel "Boost on UI" behavior, which is almost certainly unnecessary. 01.17.49 # <[Saint]> Hmmm. 01.17.55 # <[Saint]> Good catch there. 01.18.01 # * [Saint] pats himself on the back 01.18.43 # <[Saint]> This might make a /slight/ difference in battery life, moreso with heavy UI interaction. 01.19.09 # <[Saint]> Its extremely likely that the Nano2G doesn't need this either. 01.19.42 # <[Saint]> Hmmm, maybe not. That's got a much lower minimum clock. 01.26.35 # <[Saint]> TheSeven: how feasible would multiple levels of boost for the Classic (and others) be do you think? 01.27.15 # <[Saint]> going from 54MHz to ~200+ on UI interaction seems more than a little insane. 01.27.24 # there are 2 ways how boost can be implemented: 1. by changing clock dividers, 2. by changing pll multipliers 01.27.57 # 1. only works in integer or even power-of-2 steps, 2. has several milliseconds of latency and might mess with audio playback 01.28.33 # so there's an easily accessible 108MHz clock in between, but anything else between 54 and 216 might be problematic 01.29.00 # <[Saint]> also, what'd be the best way to do it? watch some thread, step up if it starts to choke, step down when its kosher again; repeat? 01.29.01 # I'm wondering if unboosting makes any sense at all on this platform though 01.29.43 # these processors have very efficient sleep modes, so unless you're busy waiting for something reducing the core clock shouldn't save much power 01.29.47 # <[Saint]> Why is that? There's almost no need to boost at all. 01.30.04 # <[Saint]> gah, lag. 01.30.26 # there is a difference if you can do undervolting to an even lower level at the lower clocks 01.30.39 # but that might again have serious amounts of latency 01.31.50 # <[Saint]> Hmmm...well, perhaps there are some targets that could benefit here if I motivated myself enough to get a WIP solution implemented. 01.32.09 # <[Saint]> Our current "all or nothing" boost seems odd and inefficient to me. 01.32.31 # <[Saint]> I'm thinking something akin to an ondemand governor. 01.33.31 # <[Saint]> The guts of deciding when to boost up/down is simple - working out different clock steps for each target I may falter on, though. 01.34.42 # <[Saint]> TheSeven: re: undervolting - have you had much luck there? If so, with which values? 01.35.01 # <[Saint]> I tried very briefly, with absurdly instable results. 01.38.37 # it works somewhat well on the nano2g, but it seems like there isn't much gain from lowering the clocks 01.38.53 # no idea on the classic, that has been unstable as shit due to i2c race conditions 01.44.43 # <[Saint]> Playing with the Classic now without GUI boosting - no observable difference, as expected. 01.45.31 # <[Saint]> I doubt it will make any notable difference in battery life, but, needlessly boosting can't really be a "Good Thing (TM)". 01.47.10 Join r0b- [0] (~rob@unaffiliated/r0b-) 01.47.29 # why is the mouse disabled in Rockbox for the Sansa Clip + ? 01.47.54 # <[Saint]> I suspect this patch predates the N2G being stable (haven't looked at the date, but I recall it being around 2008 if memory serves), and definitely predates the Classic. 01.52.01 # <[Saint]> r0b-: its not just the mouse. 01.52.10 # <[Saint]> Its all HID. 01.52.14 # why! 01.52.15 # :) 01.52.35 # <[Saint]> because you haven't enabled it yet? :) 01.52.54 # how do i enable it 01.54.42 # <[Saint]> Sorry - that was a bit mean. That was a failed humorous attempt at saying "its not implemented for this target, and this still needs to happen - you could do so, given enough time and education". 01.54.50 # <[Saint]> Its not an on/off switch type of thing. 01.55.08 # :P 01.58.50 # you guys know how the ipod can emulate a mouse right? is there anybody that feels up to either telling me how to make or make it emulate a mouse left click with variable frequency? (maybe use the wheel for frequency and a button to be on or off and another one for temporary) 02.00.02 # <[Saint]> teehee - the Classic defines HAVE_USB_HID_MOUSE 02.00.16 # <[Saint]> No, Classic, ...you can't do that. 02.02.02 # i could just toss a 555 in my old mouse and call i it a day but the ipod would be fun :) 02.02.15 # <[Saint]> SuperBrainAK: at a guess, I'd say you want to be nosey at /firmware/usbstack/usb_hid.c 02.02.43 # what language is it? 02.03.08 # <[Saint]> C 02.03.42 # ok thats what i know :) 02.05.28 Quit Xerion (Ping timeout: 264 seconds) 02.06.43 # * SuperBrainAK grabs his old laptop 02.06.51 # oh god :P 02.07.07 # dont encourage him. 02.07.45 # hey its running linux :) the rest run w7 or higher :P 02.07.59 # * r0b- will BAN u from this game! 02.08.11 Join Xerion [0] (~xerion@5419F5F4.cm-5-2d.dynamic.ziggo.nl) 02.11.39 Join SuperBrainAK_ [0] (~Andy@71-36-163-249.phnx.qwest.net) 02.13.16 Quit SuperBrainAK_ (Client Quit) 02.17.42 Quit krabador (Quit: Sto andando via) 02.19.12 *** Saving seen data "./dancer.seen" 02.19.17 Join krabador [0] (~krabador_@unaffiliated/krabador) 02.28.09 # so i have to write the HID code for the clip + ? 02.28.18 Join SuperBrainAK_ [0] (~Andy@71-36-163-249.phnx.qwest.net) 02.29.30 Nick SuperBrainAK_ is now known as SuperBrainAKEee (~Andy@71-36-163-249.phnx.qwest.net) 02.33.08 # ok i have hopefully logged in as me 02.34.20 # <[Saint]> you have, yes. 02.35.11 # sweet, but i did accidentally paste the whole jane doe :D 02.40.20 # so im thinking i need to be at line 325 it seems 02.53.37 Part r0b- ("Leaving") 02.56.59 # so what variable is it that is the scroll wheel? im assuming it is some variable controlled by another code file that outputs a "i am changing bit" and speed and direction? 03.02.02 Quit Epicanis (Ping timeout: 276 seconds) 03.23.53 Quit Zarggg (Read error: Connection reset by peer) 03.24.25 Join Zarggg [0] (~zarggg@24.229.140.62.res-cmts.sm.ptd.net) 03.28.01 Part micah 03.36.42 Quit krabador (Ping timeout: 260 seconds) 04.05.08 # i think i might just use my teensy ++ that way i can use an old button board to a tv and have different frequencies set 04.05.34 Quit SuperBrainAKEee (Remote host closed the connection) 04.07.45 Quit derf (Read error: Connection reset by peer) 04.19.15 *** Saving seen data "./dancer.seen" 04.21.49 Join webguest59 [0] (~18930ff2@www.haxx.se) 04.21.53 # hello 04.21.58 Quit webguest59 (Client Quit) 04.23.17 # <[Saint]> ...bye. 04.27.01 Quit amiconn (Disconnected by services) 04.27.02 Join amiconn_ [0] (amiconn@rockbox/developer/amiconn) 04.27.07 Nick amiconn_ is now known as amiconn (amiconn@rockbox/developer/amiconn) 04.27.15 Quit pixelma (Disconnected by services) 04.27.16 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 04.27.19 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma) 04.55.41 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 05.16.57 Join Rower [0] (husvagn@v-413-alfarv-177.bitnet.nu) 05.17.02 Join derf [0] (~derf@fuzzyneural.net) 05.45.23 Quit TheSeven (Disconnected by services) 05.45.32 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 05.58.23 # <[Saint]> Would it help anyone any if I made a generic device config template? 06.00.45 # <[Saint]> I'm sure I'm not the only one that has noticed the various device configs are in a massive mess. 06.01.55 # <[Saint]> It doesn't change a thing for existing targets, but possibly having all the configs ordered in a sane way would make it easier for those new to the code, or a specific port, to spot defines without having to grep for things they may not know exists, or read the entire config file. 06.04.30 # <[Saint]> Hmmmm...no...doing that might just make it even easier for people to just c/p and include defines that aren't needed. Bah. 06.05.46 # :) 06.07.28 # <[Saint]> Stick around long enough and you'll eventually see I talk myself out of a lot of my "good ideas" without any feedback from anyone else. 06.07.39 # <[Saint]> I'm a one man debate team. 06.13.00 # lol 06.19.18 *** Saving seen data "./dancer.seen" 07.47.46 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 07.50.01 Quit tchan (Quit: WeeChat 0.4.1) 07.59.36 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 08.14.42 Quit pamaury (Ping timeout: 276 seconds) 08.19.21 *** Saving seen data "./dancer.seen" 08.22.38 Join ender` [0] (krneki@foo.eternallybored.org) 08.39.52 Join tapiralec [0] (~alec@cpe-76-184-243-233.tx.res.rr.com) 08.40.08 Quit tapiralec (Read error: Connection reset by peer) 08.40.58 Join tapiralec [0] (~alec@cpe-76-184-243-233.tx.res.rr.com) 08.53.43 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 08.57.47 Nick SuperBrainAK is now known as DormantBrain (~andy@shared02.balt01.cd.2g2u.net) 08.57.51 Join habys [0] (~luke@arikui.org) 08.58.46 Quit tapiralec (Remote host closed the connection) 08.59.03 Join tapiralec [0] (~alec@cpe-76-184-243-233.tx.res.rr.com) 09.05.11 Quit rdn (Read error: Connection reset by peer) 09.13.51 Quit tertu (Ping timeout: 276 seconds) 09.19.37 Join lorenzo92 [0] (~chatzilla@host242-106-dynamic.17-79-r.retail.telecomitalia.it) 09.21.47 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 09.23.44 Quit bertrik (Read error: Operation timed out) 09.26.46 Join petur [0] (~petur@rockbox/developer/petur) 09.39.30 Quit bluebrother^ (Ping timeout: 246 seconds) 09.40.39 Quit fs-bluebot (Ping timeout: 264 seconds) 09.41.34 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 09.42.09 Join fs-bluebot [0] (~fs-bluebo@g224239059.adsl.alicedsl.de) 09.59.45 # <[7]> [Saint]: have you looked at the modular design that I used in the UMSboot source code that I linked above? 10.00.29 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 10.11.09 # <[Saint]> [7]: I haven't, no, what in particular are you referring to? 10.11.19 # <[Saint]> My phone doesn't want to give me that much scrollback. 10.13.56 # <[7]> https://mega.co.nz/#!4Iw3USyD!EK2O-Q-jdumd6xYPeb1FVwfyh0x-tR0ljUvA2AfGU7M 10.19.25 *** Saving seen data "./dancer.seen" 10.22.42 # <[Saint]> Ooooooh - very nice. 10.22.52 # <[Saint]> Is it booting on N2G yet? 10.23.37 # <[Saint]> All my N2Gs flatly refuse to update emCORE presently, so, I'll be happy to test when you're ready. 10.24.05 # <[Saint]> I have some handrolled-by-you, non-release-version on all mine. 10.24.20 # <[Saint]> [7]: ^ 10.31.20 # <[7]> [Saint]: yes, that's working on n2g just fine 10.31.28 # <[7]> just doesn't have an LCD driver yet, I'm working on that 10.31.38 # <[7]> once that's done I'll port it to the classic 10.32.36 # <[Saint]> [7]: question for both Classic and N2G - could we jump to diagmode from the emCORE menu? 10.32.47 # <[Saint]> (vastly more useful for the Classic than the N2G) 10.34.22 # <[7]> yes, that can be done 10.34.36 # <[7]> I think I removed it for flash space reasons 10.34.43 # <[Saint]> Ah. 10.34.51 # <[7]> but you should be able to just drop it as a .ubi file into diagmode 10.34.56 # <[7]> er into UMSboot 10.35.21 # <[7]> on the nano2g it should already be present 10.36.46 # <[Saint]> Perhaps it is, maybe I'm misremembering - but I don't recall seeing it as an option. 10.37.15 # <[Saint]> As I said, though, I do have some "pretty much as soon as you got it booting" very early emCORE version on there. 10.37.19 # <[7]> it's hiding in the tools menu 10.37.39 # <[Saint]> Was this implemented at a later stage perhaps? 10.37.45 # <[7]> quite possibly 10.41.58 Join lebellium [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 10.48.11 Join jlbiasini [0] (~metaphysi@89.136.132.239) 10.56.47 # pamaury: ping 10.58.15 # jlbiasini: pong 10.59.33 # pamaury: g#525 should be ready now if it's ok you can push it after g#529 (it depends on it) 10.59.36 # 3Gerrit review #525 at http://gerrit.rockbox.org/r/525 : 3[Fuze+][Touchpad] Improve touchpad power managment by Jean-Louis Biasini (changes/25/525/5) 10.59.37 # 3Gerrit review #529 at http://gerrit.rockbox.org/r/529 : 3[RMI Driver] Implement power saving support by Jean-Louis Biasini (changes/29/529/3) 11.01.20 # I tested it but I didn't find a way to have the debug screen showing if the down to very_low_power mechanism was working... 11.01.39 # as it is in the other loop... 11.04.49 # is this reporting rate code in the debug screen really needed ? 11.05.03 # pamaury: I'm also wondering about the name of touchpad_enable() if it is the function meant to be use to disable the touchpad on keylock, I would rather have it named touch_device_enable() for consistency reason with other touchscreen 11.06.29 # well reading the register anyway I though it was nice to report all its value, why? 11.06.47 # actually the code also offer to change the report rate value 11.06.58 # no I mean, why is there some code which changes the report rate based on sensibility ? 11.08.01 # aha no, the sensibility_counter is just a counter to avoid change from vol key to be to sensible 11.08.57 # the patch change the old vol keys for setting sensitivity (we have a setting for that now) to vol key for either power mode or report rate 11.09.43 # change 11.10.26 # hum, I would prefer to only change the power mode, and use a more sensible range than -15..15. For example 1 would be fully awake, 0 would be normal, -1 low power, -2 very low power, -3 sleep. 11.10.45 # doesn't that seem more logical ? 11.11.59 # pamaury: yes I just used the hrd values, regarding sensibility I tested it and it seems to me enough 11.12.33 # And I know I am stubborn but I am still not convinced that changing the report rate is a win. 11.12.47 # By the way: did we fix the sensibility setting range ? I don't remember... 11.13.07 # ?? did it has to be fixed? 11.13.21 # *had 11.13.45 # 25 to -25 is good for what I know 11.13.54 # ah ok, we changed it to -25..25, good 11.15.05 # I've commented on the rmi patch: it's ok except for style. The other one is basically ok, except for style and 1) report rate 2) this code in the debug screen. I'll publish the comments in a minute 11.15.06 # pamaury: another thing is the low_power mode as standard, the doc actually says that on device that doesn't implement gesture like double tap & co it should be standard 11.16.17 # regarding report rate, I think only a battery_bench can say 11.19.18 # ah ok, well on thing is sure (that's my understanding of the spec and it can be checked using the IRQ debug screen): 1) if you don't touch the pad, the device reports nothing so report rate is irrelevant; 2) if the pad is disabled, the device reports nothing so report rater is irrelevant; 3) otherwise the screen will be on because touchpad is on and report rate costs a lot less than backlight, so it's mostly irrelevant 11.20.17 # Or at least, we can tweak the report rate as part of another commit if it appears that it changes the battery life, does that seem fair ? 11.21.03 # pamaury: + actually pperforming at a lower rate is not confortable on the fuze+ so lets drop that 11.21.44 # the doc says: "This field sets the report rate for the device. It applies in common to all functions on the 11.21.44 # device that have a natural report rate. " 11.23.27 # I've published some comments, should be easy to fix 11.23.50 # I know i'm a bit harsh about style but we try to keep consistent style in each file, otherwise it's a mess 11.23.50 # :) 11.25.07 # pamaury: that's ok It's usefull for me to learn the clean way. Regarding touch_device_enable is that ok? 11.25.54 # I'm not decided, but you might be right for this one 11.25.58 # going for lunch, see you later 11.29.32 # some early lunch 11.33.53 # * [Saint] wonders how he could reliably benchmark this slight change to the Classic 11.33.59 # <[Saint]> (turning off GUI boosting) 11.34.25 # <[Saint]> I don't suspect it will make a large, or even very noticeable, difference..but, I'd like to know. 11.35.21 # <[Saint]> maybe I can use a raspberrypi, a servo, and a capacitive touchpen to twiddle with the clickwheel in a repeatable fashion? 11.35.49 # <[Saint]> that's the thing. The UI needs to be in use, and it needs to be used consistently. 11.36.09 # <[Saint]> Very hard to test this manually. And the device just sitting idle doing nothing shows me nothing. :-S 11.38.34 Quit [Saint] (Remote host closed the connection) 11.39.40 Join [Saint] [0] (~saint@rockbox/user/saint) 12.05.50 Join stoffel [0] (~quassel@pD9E4166C.dip0.t-ipconnect.de) 12.19.26 *** Saving seen data "./dancer.seen" 12.20.50 Quit michaelni (Quit: Leaving) 12.29.53 Join michaelni [0] (~michael@chello080109127209.4.15.vie.surfer.at) 13.13.04 Join krabador [0] (~krabador_@unaffiliated/krabador) 13.13.35 Quit [Saint] (Remote host closed the connection) 13.13.40 # [Saint]: I'd just make the change and see if it breaks anything 13.13.50 # if it doesn't, commit it, I guess 13.14.25 # or, if it's supposed to make little difference in practice, maybe don't bother? 13.14.42 Join [Saint] [0] (~saint@rockbox/user/saint) 13.14.51 # great copper 13.15.09 # [Saint]: I was talking to you right after you quit 13.15.15 # 11:13:41 UTC [Saint]: I'd just make the change and see if it breaks anything 13.15.18 # 11:13:51 UTC if it doesn't, commit it, I guess 13.15.20 # 11:14:26 UTC or, if it's supposed to make little difference in practice, maybe don't bother? 13.21.10 # jlbiasini: you forgot to fix the style of the if in the rmi patch ;) 13.21.28 # arfff 13.21.30 # ok 13.22.02 # * copper is trying to remember what he wanted to ask pamaury 13.22.46 # see my comment on the other commit 13.22.47 # ah yes 13.23.07 # pamaury: is there any way to make the sdcard reader in the Fuze+ faster? 13.23.53 # copper: not sure, is the read/write speed much slower compared to actual card speed ? 13.24.03 # writing is twice slower 13.24.07 # with my sdxc card 13.24.18 # hum, and reading ? 13.24.22 # dunno 13.25.09 # jlbiasini: which comment ? 13.25.18 # copper: can you check that too ? That would help 13.25.28 # ok 13.25.42 # I made a comment but it is showed as draft 13.25.58 # you need to say review and publish comment to display them 13.26.07 # ok 13.26.52 # meanwhile the rmi part is rerererecorrected ;) 13.27.31 # jlbiasini: I have a last comment on the rmi part, I'll add it, it will take 1 minute to fix and then i'll commit 13.27.47 # ok 13.29.12 # not let me read the comment 13.29.16 # *now 13.29.37 # copper: how did you check the speed ? using usb or the test_disk plugin ? 13.29.49 # hum I don't see your comment yet 13.32.22 # pamaury: now it should be readable 13.33.15 # pamaury: dd on the sdxc device of the Fuze+ connected via USB 13.33.42 # what does BM stand for? 13.33.43 # reading is over twice slower via the Fuze+, compared to the sdxc adapter in my laptop's sdcard reader 13.34.03 # 8.3 MB/s vs. 19.7 MB/s 13.34.21 # Bit Mask 13.34.46 # ahah 13.34.51 # copper: ok, do you happen to have the test_disk plugin on your fuze+ or not ? 13.35.24 # yes 13.36.11 # can you run it to see the result ? 13.36.16 # ok so obviously I have to use them in button-fuzeplus.c too 13.36.17 # running it 13.36.21 # jlbiasini: indeed, your comment looks relevant 13.36.35 # jlbiasini: where is it needed ? 13.38.52 # pamaury: does test_disk produce a log file? 13.39.02 # yes iirc 13.40.06 # http://pastebin.com/QU9y9QMD 13.40.39 Join n1s [0] (~n1s@nl118-168-30.student.uu.se) 13.40.39 Quit n1s (Changing host) 13.40.39 Join n1s [0] (~n1s@rockbox/developer/n1s) 13.41.18 # ok so it's not usb related (I had no doubt but I just wanted to check). I'll have a look at this issue 13.41.56 # pamaury: note that I'm using a class 10 microsdxc card (64 GB), if that makes any difference 13.42.22 # which one is onboard flash, and which one is sdcard (A or U)? 13.43.17 # ah damn, I didn't think about this: test_disk probably only benchmark the internal storage. A is append, U is update I think so unrelated :-/ 13.44.00 # Aligned, unaligned, I'd expect 13.44.20 # yeah, more likely 13.44.59 # hum, ok i'll the test by myself and see what I can do about this issue 13.46.23 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 13.50.41 Quit stoffel (Remote host closed the connection) 13.51.17 Join stoffel [0] (~quassel@pD9E4166C.dip0.t-ipconnect.de) 13.53.42 # pamaury: so are all part of the comment relevant or which ones? what is where needed? 13.54.35 # pamaury: you pastebin patch seems ok, all the other comments of mine still apply 13.54.59 # I had forgotten about the vol key delay, it's much better in your patch 13.58.00 # <[7]> lol 13.58.11 # <[7]> "note to self"? :P 13.58.19 # yes it's because I was trying to reuse the old one where having signed value allow to add it directly to sensistivity with a division, thus avoiding a recheck on wether it was vol up or vol down 13.58.54 # the patch is nearly ready I was waiting for your reply on the comment before going on 13.59.40 # go on, update the patch, and try to take all my other comments into account ^^ 14.00.17 # you forgot to add: "I dare you" ;D 14.02.02 # haha 14.11.06 Quit derf (Ping timeout: 246 seconds) 14.12.08 Join derf [0] (~derf@fuzzyneural.net) 14.16.54 # pamaury: done 14.19.27 *** Saving seen data "./dancer.seen" 14.28.17 # pamaury: there still no link on rb main page to zen? I though they could be in unstable? 14.28.25 # Build Server message: 3New build round started. Revision be72c4f, 217 builds, 18 clients. 14.29.41 # jlbiasini: zen is not in the trunk 14.30.11 # ok 14.31.19 # I will have to add a silent function to all touch device now, if I want this touchdev disable on lock 14.32.30 # did you test all the patches ? 14.32.51 # you mean the ones I just commited yes 14.33.36 # but I is not possible to knox if the touchpad is actually lowering after one minute... 14.36.20 Join amayer [0] (~amayer@mail.weberadvertising.com) 14.36.32 # Build Server message: 3Build round completed after 487 seconds. 14.37.14 # jlbiasini: it would be possible if the debug screen read the power value each time 14.39.35 # ok 14.39.45 # still something to add then 14.45.52 # pamaury: well that would be tough anyway... the backlight goes down and to have it backup without the touchpad it volume key or power... 14.46.10 # :( 14.49.04 # pamaury: no it does works! even if the volume keys are touch as long as no activity on the touchpad occurs it set it back to the very_low_power 14.53.56 # pamaury: ok I commited a fix 14.54.10 # jlbiasini: you can set backlight timer to 1min+ 14.54.56 # anyway it's no needed we can get the backlight by volume key 14.56.04 # jlbiasini: last tweak and then you are done, would be better if you can test it, you can reduce the activity timeout when testing to avoid the long wait 14.58.04 # pamaury: I have question: with that mechanism won't power state goes back to very_low_power mode after no activity occurs and the touchpad has been set to sensor_slepp :/ 14.59.56 # hum, that's right 15.00.25 # lol 15.01.38 # I see two ways of fixing this: 1) have a boolean which hold the activation state 2) implement rmi_get_sleep_mode() and only go to very_low_power if sleep_mode is not sleep 15.03.41 # maybe 1) is better 15.04.04 # so in touchpad enable I set a boolean 15.04.20 # yes 15.04.48 # and recheck it before going to very_low 15.05.14 # yes 15.06.21 # that would work but not in the debug screen. Is that a problem? 15.07.51 # no, debug screen is for debug, use it at your own risk 15.09.20 # regarding the change in the timeout I was thinking to have a ACTIVITY_TMO_DEBUG to use unstead of the standard one. But how can I check if I'm in the debug screen from the rmi thread? 15.11.49 # you cannot really 15.15.39 # pamaury: should I add another bool debug mod? 15.17.10 Quit x56 (Ping timeout: 240 seconds) 15.17.29 Quit liar (Read error: Connection reset by peer) 15.18.29 # kugel: now i'm working on something else, BUT, how do you think it's better to move? fix the issue or simply write a simpler usb "stack" for hosted targets? 15.18.41 # of course the first would be the best but... 15.18.57 Join x56 [0] (~0x56@sillytitties.com) 15.19.49 # could it be also a problem related to threading? just a guess... 15.22.51 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 15.23.32 # jlbiasini: I'm not sure this is worth it 15.34.17 Quit habys (Ping timeout: 245 seconds) 15.36.01 Join habys [0] (~luke@arikui.org) 15.37.22 # jlbiasini: or make this activity timeout a setting :p 15.45.17 Quit amayer (Quit: Leaving) 15.45.55 # pamaury: you launch the discution about it. When you will be done i'll start implementing ;D 15.48.22 # It's a half serious question. I wonder what is optimal value of this activity timeout. The valid options I see are 1) same as backlight timeout 2) some hardcoded value which work well 3) some dedicated value with a setting 15.49.46 # and there is 4) = any of 2) or 3) + automatically switch to very_low_power when the lcd is off 15.50.14 # because it kind of makes sense to lower the power when nothing is displayed, don't you agree ? 15.54.30 # jlbiasini: I have another idea, because the whole points comes down to one thing really: is the transition from very_low_power to low_power fast enough ? Suppose that it is, then if you immediately switch to low_power when the user touches the pad, it will not even notice the difference. 15.55.19 # I think I need to experiment by myself tonight before making a decision 15.57.56 Quit DexterLB (Read error: Connection reset by peer) 15.57.59 Join Dexter_LB [0] (~dex@77-85-0-255.btc-net.bg) 16.05.32 Quit Dexter_LB (Read error: Connection reset by peer) 16.05.38 Join DexterLB [0] (~dex@77-85-0-255.btc-net.bg) 16.05.39 # pamaury; the user setting is useless because the user will not make any difference anyway. The backlight idea seems fair 16.06.47 Join thegeek [0] (~thegeek@40.200.16.62.customer.cdi.no) 16.06.51 Quit thegeek_ (Read error: Connection reset by peer) 16.08.10 # the direct transition seems also a fair idea but I will have to test it during the game too to make sure it doesn't bother 16.08.46 # yeah, we need some tests to see if one can notice the transition or not 16.09.26 # what I tested is very_low_power by itself and it wasn't good enough 16.15.43 Join tertu [0] (~tertu@65-128-181-81.mpls.qwest.net) 16.19.29 *** Saving seen data "./dancer.seen" 16.27.25 Quit pamaury (Ping timeout: 240 seconds) 16.33.33 Quit n1s (Quit: Ex-Chat) 16.48.01 Join n1s [0] (~n1s@rockbox/developer/n1s) 16.57.08 Quit [Saint] (Read error: Connection reset by peer) 16.58.06 Join [Saint] [0] (~saint@rockbox/user/saint) 17.12.15 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 17.15.23 Join ikeboy [0] (~dell@ool-435622d3.dyn.optonline.net) 17.28.17 # pamaury: from what I can test I don't see any difference indeed... so we could set it to 5 * HZ just to avoid useless change and we are done... 17.28.51 # i tested with HZ 17.28.51 Quit ikeboy (Ping timeout: 246 seconds) 17.29.26 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 17.30.52 # pamaury: And if you read the golden quote you should know that we don't need extra tests... As far as I know both of us already has 2... 17.32.09 Join amayer [0] (~amayer@mail.weberadvertising.com) 17.37.19 Quit krabador (Quit: Sto andando via) 17.40.19 Quit petur (Quit: Nettalk6 - www.ntalk.de) 17.43.12 Join ikeboy [0] (~dell@ool-435622d3.dyn.optonline.net) 17.51.07 # <[7]> [Saint], pamaury: the LCD driver (and related stuff) has landed, so I'd say the nano2g part is finished :) 17.51.17 # <[7]> anyone around for nano2g usb stress testing? 17.52.33 # <[Saint]> gah - unfortunately, I cannot now get to my treasure chest of devices tucked away in the closet without waking up Ms [Saint] 17.53.07 # <[Saint]> were it not 4am, this wouldn't be an issue. 17.53.24 # <[7]> well, this can wait until tomorrow :) 17.53.33 # <[7]> I have a whole ipod classic port to do... 17.53.43 # <[Saint]> bah. 17.53.58 # <[Saint]> *those* are right next to me... 17.54.01 # <[Saint]> :) 17.54.19 # <[7]> so, what do we need for this to work on the classic? 17.54.33 # <[Saint]> Hmmm? 17.54.54 # <[7]> (i.e. sl8720 chipset support + ipod classic LCD support and other peculiarities) 17.55.05 # <[Saint]> aha. 17.56.21 # <[7]> someone interested in reading the source code, or should I go ahead and do the classic port before updating the source? 17.56.39 # <[Saint]> Is emCORE going to be pushed as the official N2G bootloader? 17.56.52 # <[7]> I see no reason to do that 17.58.54 # <[Saint]> I seem to recall the bootloader USB being completely wonky. 17.59.16 # <[7]> there's no need for bootloader USB *at all* on the N2G 17.59.17 # <[Saint]> I can't recall if it was ever fixed before N2Gs USB died completely. 17.59.36 # <[7]> well, the plan is to finally fix N2G USB 18.00.35 # <[Saint]> Hum. This is so many years ago. I may misremember this. 18.00.48 # <[Saint]> There's a chance I kludged bootloader USB in there. 18.01.34 # <[Saint]> it isn't needed, due to OF/disc mode, but - its kinda handy. 18.05.32 Join mrtux_ [0] (~colin@75-167-98-77.desm.qwest.net) 18.06.06 Quit mrtux_ (Changing host) 18.06.06 Join mrtux_ [0] (~colin@unaffiliated/mrtux) 18.09.09 Quit mrtux (Ping timeout: 264 seconds) 18.09.10 Nick mrtux_ is now known as mrtux (~colin@unaffiliated/mrtux) 18.17.22 Quit ikeboy (Quit: Ex-Chat) 18.19.32 *** Saving seen data "./dancer.seen" 18.25.06 Quit habys (Ping timeout: 245 seconds) 18.26.00 Quit [Saint] (Remote host closed the connection) 18.26.47 Join habys [0] (~luke@arikui.org) 18.26.58 Join [Saint] [0] (~saint@rockbox/user/saint) 18.27.00 Join y4n [0] (~y4n@unaffiliated/y4ndexx) 18.33.11 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 18.42.06 Join belak [0] (~belak@facebook/engineering/belak) 18.50.48 Join thegeek_ [0] (~thegeek@40.200.16.62.customer.cdi.no) 18.54.02 # is there ANY touchscreen device with softhold? just tried mrope500, cowond2 18.54.12 Quit thegeek (Ping timeout: 256 seconds) 18.59.26 # hey I found one!!! VX777 and the simulator doesn't compile!! 19.00.22 # keymaps uncomplete on a plugin!! 19.00.49 # That's interesting 19.00.57 # The main build does seem to compile 19.01.34 # it's missing TOUCHSCREEN_QUIT and TOUCHSCREEN_TOGGLE define 19.04.40 # http://paste.debian.net/19599/ 19.04.45 # * scorche|sh takes away jlbiasini's exclamation mark key 19.04.47 # That seems to fix it 19.05.14 # I know I'm about to push the same to gerrit 19.05.53 # Ah, good. I won't commit then 19.06.03 # Pushing a button on gerrit is less work :) 19.06.31 # g#531 19.06.35 # 3Gerrit review #531 at http://gerrit.rockbox.org/r/531 : 3[ONDAV VX777][simulator] fix missing keymaps in test_touchscreen by Jean-Louis Biasini (changes/31/531/1) 19.07.21 # Build Server message: 3New build round started. Revision f285a0f, 217 builds, 19 clients. 19.11.12 # jlbiasini: also R1 by the way, I'm going to polish my raw patches ^^ 19.11.34 Join ikeboy [0] (~dell@ool-435622d3.dyn.optonline.net) 19.14.33 Quit Poodlemastah_ (Read error: Connection reset by peer) 19.15.04 # Build Server message: 3Build round completed after 465 seconds. 19.15.05 Join Poodlemastah [0] (~Poodlemas@109-124-181-96.customer.t3.se) 19.16.22 Quit Rower (Quit: Hmmm...) 19.20.16 Quit mrtux (Read error: Connection reset by peer) 19.22.15 Join mrtux [0] (~colin@75-167-98-77.desm.qwest.net) 19.22.17 Join Rower [0] (husvagn@v-413-alfarv-177.bitnet.nu) 19.27.29 Quit ikeboy (Remote host closed the connection) 19.36.10 Join ikeboy [0] (~dell@ool-435622d3.dyn.optonline.net) 19.36.57 Join krabador [0] (~krabador_@unaffiliated/krabador) 19.36.59 Quit stoffel (Read error: Operation timed out) 19.40.57 Join pretty_function [0] (~sigBART@123.252.214.21) 19.52.58 Quit krabador (Ping timeout: 260 seconds) 19.54.56 # <[7]> impressive 19.55.10 # <[7]> the ipod classic port compiled first try without warnings 19.55.14 # <[7]> now if it would just work... 19.56.07 # ? 19.56.15 # it always does 19.56.19 # recently, anyway 20.05.57 Join krabador [0] (~krabador_@unaffiliated/krabador) 20.14.17 Quit pamaury (Read error: Connection reset by peer) 20.17.52 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 20.19.34 *** Saving seen data "./dancer.seen" 20.23.21 # jlbiasini: ping 20.29.46 Join einhirn [0] (Miranda@bsod.vpn.tu-clausthal.de) 20.40.28 Quit ikeboy (Quit: Ex-Chat) 20.42.50 Quit shamus (Read error: Connection reset by peer) 20.43.16 Join shamus [0] (~shmaus@ip-206-192-195-49.marylandheights.ip.cablemo.net) 20.47.33 Quit krabador (Quit: Sto andando via) 20.56.00 Quit shamus (Read error: Connection reset by peer) 20.57.18 Join shamus [0] (~shmaus@ip-206-192-195-49.marylandheights.ip.cablemo.net) 21.15.30 Quit Zarggg (Ping timeout: 240 seconds) 21.22.47 Quit pretty_function (Remote host closed the connection) 21.22.52 Quit Xerion (Quit: ) 21.25.45 Join rdn [0] (~oop@cpe-69-204-124-212.buffalo.res.rr.com) 21.31.53 Join evilnick_ [0] (~evilnick@d54C370E0.access.telenet.be) 21.32.10 Join dokan_ [0] (~minatani@ac250006.ppp.asahi-net.or.jp) 21.32.11 Quit dokan (Ping timeout: 246 seconds) 21.32.11 Quit evilnick (Ping timeout: 246 seconds) 21.33.07 Quit JdGordon (Ping timeout: 246 seconds) 21.33.08 Join JdGordon_ [0] (~jonno@CPE-121-218-128-145.lnse3.cht.bigpond.net.au) 21.33.08 Quit JdGordon_ (Changing host) 21.33.08 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 21.34.09 Join stoffel [0] (~quassel@pD9E4166C.dip0.t-ipconnect.de) 21.37.49 Join freqmod_ [0] (~quassel@cm-84.215.142.108.getinternet.no) 21.38.24 Quit freqmod (Ping timeout: 246 seconds) 21.43.57 # <[7]> wow, that was quicker than I had thought 21.43.58 # <[7]> https://mega.co.nz/#!tAYmxZoC!UF9c3W8W0Jqk0kZszgGNkE_dlxBlPvtah_tFFPdQFJA 21.44.08 # <[7]> now supports nano2g and classic 21.44.38 # <[7]> pamaury: ^ 21.45.58 Join thomasjfox [0] (~thomasjfo@rockbox/developer/thomasjfox) 21.55.59 Quit lorenzo92 (Quit: ChatZilla 0.9.90.1 [Firefox 22.0/20130712032019]) 21.59.11 Quit mrtux (Changing host) 21.59.11 Join mrtux [0] (~colin@unaffiliated/mrtux) 21.59.54 # [7]: is it stable on nano2g 21.59.54 # ? 22.00.09 # <[7]> as far as I can tell yes 22.00.46 # <[7]> but I wasn't affected by those problems people keep reporting all the time in the first place, so it needs more testing 22.02.31 # <[7]> and, guess what, even the current rockbox ipod classic build works fine here. hm... 22.06.39 # <[7]> the nano one locks up though 22.07.43 # <[7]> are there ANY iPod Classic users here, who are having trouble accessing a current build via USB? Or trouble accessing UMSboot on Classic or Nano 2G? 22.08.58 # not me 22.09.09 # current build works fine 22.12.26 # [7]: i havent had any problems accessing USB on my current build of iClassic 22.19.16 Quit shamus (Read error: Connection reset by peer) 22.19.38 *** Saving seen data "./dancer.seen" 22.20.18 Join shamus [0] (~shmaus@ip-206-192-195-49.marylandheights.ip.cablemo.net) 22.20.59 Quit saratoga (Ping timeout: 250 seconds) 22.33.37 Quit y4n (Quit: PANTS OFF!) 22.36.08 Join Xerion [0] (~xerion@5419F5F4.cm-5-2d.dynamic.ziggo.nl) 22.38.00 # pamaury: pong 22.40.30 # I have commented your patch 22.41.15 # We still to experiment but you can already correct this 22.41.20 # *need to 22.42.58 # pamaury: I might not have time before 1 or two weeks but I'll try 22.43.11 # ok, then i'll try 22.44.45 # pamaury: as you want actually. I'm still wanting to do it but I'll travel over ten days starting with thirsday (basically i'm going back to france across austria... 22.45.15 # so it actually depends on the equipment od the train i'll be into 22.45.51 # either I'll be all done saturday either i'll do it in france 22.49.02 Quit jlbiasini (Quit: jlbiasini) 23.00.50 Quit thomasjfox (Quit: Konversation terminated!) 23.02.03 Quit amayer (Quit: Leaving) 23.05.02 Quit kevku (Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/) 23.10.08 Join jlbiasini [0] (~metaphysi@86.34.67.25) 23.10.38 # pamaury: well I will see what I can do now 23.14.41 Quit stoffel (Ping timeout: 245 seconds) 23.17.21 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 23.19.35 Quit kiwicam (Read error: Connection reset by peer) 23.19.49 Join kiwicam [0] (~quassel@101.98.163.139) 23.26.25 Quit n1s (Quit: Ex-Chat) 23.30.11 # pamaury: done! 23.31.53 # great, looks better :) 23.43.01 Quit liar (Ping timeout: 245 seconds) 23.55.47 Quit jlbiasini (Quit: jlbiasini)