--- Log for 11.03.112 Server: card.freenode.net Channel: #rockbox --- Nick: logbot_ Version: Dancer V4.16 Started: 3 days and 9 hours ago 00.00.50 Join enthdegree [0] (~BitchX@unaffiliated/enthdegree) 00.08.51 Quit ender` (Quit: Female software engineers become sexually irresistible at the age of consent, and remain that way until about thirty minutes after clinical death. Longer if it's a warm day. -- Scott Adams) 00.14.56 Quit Strife89 (Remote host closed the connection) 00.28.29 Quit ingrowntesticle (Quit: Leaving) 00.31.21 Quit randumbum (Remote host closed the connection) 00.37.04 *** Saving seen data "./dancer.seen" 00.47.28 Quit Topy44 (Ping timeout: 260 seconds) 00.56.42 Join Topy44 [0] (Topy44@f048173028.adsl.alicedsl.de) 00.59.38 Join nite [0] (~nite@74-132-255-47.dhcp.insightbb.com) 00.59.55 Nick nite is now known as Guest42952 (~nite@74-132-255-47.dhcp.insightbb.com) 01.00.07 # hello 01.00.31 Quit Guest42952 (Remote host closed the connection) 01.01.18 Join Niteshade [0] (~Nefarious@74-132-255-47.dhcp.insightbb.com) 01.02.06 # i just installed rockbox to my sansa clip+ and i want to make some programs for it. (Just for the hell of it) Where do i start? 01.03.19 # Niteshade: on the wiki probably 01.03.39 # i mean, unless you try to make a graphical program (Which, after the disaster of trying DOOM, i think i'll stick to a text interface) 01.04.07 # Niteshade: see http://www.rockbox.org/wiki/HowtoWritePlugins for example 01.04.18 # do the same rules apply as for a PC, or are there more things i should know? (BTW, my desktop is running ubuntu) 01.04.25 # oh. cool 01.05.06 # it's not the same thing but we have a posix-like interface and you can develop it using the simulator before putting it on target 01.05.28 # like, does printf("hello") print hello? 01.05.44 # i mean, what is different? 01.05.58 # nvm i will just rtfn' 01.06.03 # * rtfm 01.06.38 # yeah, read the wiki and then ask on irc :) 01.07.22 Quit pamaury (Remote host closed the connection) 01.09.10 Join Strife89 [0] (~Strife89@adsl-068-213-037-174.sip.mcn.bellsouth.net) 01.09.36 # so is there a full simple program i can just see so all these little "snippets" make more sense? 01.12.01 # and is there an emulator for linux so i can test and debug it before i put it on my player? 01.14.40 # the simulator, yes 01.15.11 # funman: should i just format the fuze? 01.15.21 # Mir: probably, yes 01.15.25 Join passstab [0] (~v@c-68-80-37-73.hsd1.pa.comcast.net) 01.15.38 # will this kill the rockbox install? 01.15.48 # where do i get this simulator? 01.16.14 Quit passstab (Client Quit) 01.16.39 Join passstab [0] (~v@c-68-80-37-73.hsd1.pa.comcast.net) 01.16.45 # Niteshade: http://lmgtfy.com/?q=rockbox+simulator 01.16.55 # thanks 01.17.23 # oh. hur hur 01.17.29 # google 01.18.28 Join dhrasmus [0] (~dhrasmus@c-76-105-237-23.hsd1.or.comcast.net) 01.25.43 # i wonder if i can find it on an apt repository 01.26.12 # Niteshade: if you want to use the simulator to test your own code, you have to build it yourself 01.27.16 # okay, AS SOON AS I FIND THE FUCKING SOURCE!!!!! 01.28.20 # hum is it that hidden? 01.28.52 # not easy to find, but i think that's not diliberate, just third-party (probably) 01.28.53 # Niteshade: 'dev guide' on the left of the site 01.30.14 # just so we're clear, when you say "the site" you mean rockbox.org right? 01.30.23 # brb getting a soda and cig 01.31.47 # back 01.32.35 Part tappi 01.34.04 # Niteshade: yes, if in doubt it's safe to assume that unspecified websites, wikis and forums here are always the rockbox ones 01.34.24 # oh fuck, it's like ipodlinux all over again 01.34.42 # i am beginning to think that this was a bad idea... 01.38.29 Join bitcraft [0] (~bitcraft@173-20-20-92.client.mchsi.com) 01.38.42 # all the dev guide is talking about is how to build rockbox. Does this mean whenever i add a plugin i have to rebuild the whole thing? 01.39.42 # no we use make which handles dependencies 01.39.52 # Yes and no. The build system is intelligent enough not to rebuild things that haven't changed 01.40.52 # i was hoping i would just be able to put it in a folder somewhere on the player 01.42.25 Quit bertrik (Quit: And That, My Liege, Is How We Know the Earth to Be Banana Shaped) 01.45.50 Quit sinthetek (Ping timeout: 244 seconds) 01.52.50 # so by your silence, i assume it's not really that easy? 01.54.11 # I don't really see how building everything is harder than building one plugin would be 01.54.12 Join tchan1 [0] (~tchan@c-69-243-144-187.hsd1.il.comcast.net) 01.56.02 # well considering that the only programs i have written don't have any build system apart from cc blah.c -x c++ -o blah 01.56.50 # plus how do i put it on the actual player? 01.56.53 Quit tchan (Ping timeout: 276 seconds) 01.57.33 Quit lebellium (Read error: Connection reset by peer) 01.57.33 Join lebellium_ [0] (~chatzilla@g231190100.adsl.alicedsl.de) 01.57.37 Nick lebellium_ is now known as lebellium (~chatzilla@g231190100.adsl.alicedsl.de) 01.57.58 # i mean, does the makefile somehow install it to the player? 01.58.35 Join Keripo [0] (~Keripo@eng334.wireless-resnet.upenn.edu) 01.59.16 # i am not what one would call a "profesional" 01.59.30 # but i can write programs in c++ 02.04.26 # better at python, but have written several full programs in c++ 02.08.42 # awesome at qbasic, good at python, alright at c++, bad at assemblty 02.08.46 # * assembly 02.14.46 Quit bitcraft (Remote host closed the connection) 02.22.21 Join bitcraft [0] (~bitcraft@173-20-20-92.client.mchsi.com) 02.28.47 Quit kadoban (Ping timeout: 260 seconds) 02.31.46 # so bad you can't even spell it 02.37.07 *** Saving seen data "./dancer.seen" 02.39.02 Join Ray072 [0] (~Ray072@75-134-123-215.dhcp.aldl.mi.charter.com) 02.42.03 Join Ray039 [0] (~Guest@75-134-123-215.dhcp.aldl.mi.charter.com) 02.45.23 Quit Ray039 (Client Quit) 02.49.03 Quit dhrasmus (Quit: Leaving) 02.50.31 # shaddap. I can read assembly, but i mean its not like you deal with it a lot, plus you have to know EVERYTHING to do ANYTHING 02.50.58 Quit Ray072 (Remote host closed the connection) 02.51.49 # something like every other month i try seriously to learn it by reading an e-book. And within the same day i usually give up 02.52.16 # due to information overload. But collectively through my attempts i think i have picked up a few tricks 02.58.28 Quit bitcraft (Remote host closed the connection) 02.59.14 Quit lebellium (Quit: ChatZilla 0.9.88.1 [Firefox 11.0/20120308162450]) 03.00.36 # i suppose i could make something in asm tho actually. I have been compiling programs into assembly (not binary, with -S) and studying them. But stuff like sockets and windows/X i could not do. 03.01.01 # or anything longer than like 20 lines probably 03.03.52 # actually no. All that super-hard memory management and working with arrays isn't for me 03.04.01 # not arrays 03.04.06 # i meant registers 03.09.07 # Niteshade: we try to keep this channel rockbox related only, but feel free to join #rockbox-community to talk about anything else 03.13.42 Quit guymann (Ping timeout: 260 seconds) 03.16.22 # sorry 03.21.02 # you don't "learn assembly", you learn about registers, flags, opcodes, adressing, etc. you have to "learn assembly" for every architecture. 03.25.05 Nick tchan1 is now known as tchan (~tchan@c-69-243-144-187.hsd1.il.comcast.net) 03.25.22 Quit tchan (Changing host) 03.25.22 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 03.27.31 Quit Strife89 (Quit: Heading home) 03.30.25 Join guymann [0] (~charles@64-252-120-203.adsl.snet.net) 03.53.13 Join factor [0] (~factor@r74-195-184-248.msk1cmtc01.mskgok.ok.dh.suddenlink.net) 03.54.22 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 04.05.55 Join curtism [0] (~curtis@bas11-montreal02-1128531121.dsl.bell.ca) 04.05.55 Quit curtism (Changing host) 04.05.55 Join curtism [0] (~curtis@unaffiliated/programble) 04.06.37 Quit passstab (Read error: Connection reset by peer) 04.07.50 Join passstab [0] (~v@c-68-80-37-73.hsd1.pa.comcast.net) 04.12.14 # jhMikeS: yes, that is why i never put more effort than casual experimentation into learning assembly. 04.13.12 # jhMikeS: well, there is a certain way of thinking you need to learn 04.14.00 # well i mean it is good stuff to know. I mean, you can go without knowing it, but knowing, i think, makes one a better programmer 04.14.35 # like how everything in a computer is numbers, it's just how its used that makes it different 04.15.14 Quit pixelma (Disconnected by services) 04.15.17 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 04.15.19 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma) 04.15.40 Quit amiconn (Disconnected by services) 04.15.40 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.16.02 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.16.34 # and the cache. I think i should make a library for C that lets you store stuff in the cache. It could be used to speed up many programs 04.17.02 # allocating some variables in the cache instead of main memory 04.17.53 # oh sorry. This isn't a programming chat. Sorry for going off-topic again 04.21.18 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 04.32.23 Join perrikwp_ [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 04.34.36 Quit perrikwp (Ping timeout: 252 seconds) 04.34.39 Nick perrikwp_ is now known as perrikwp (~quassel@cpe-024-163-024-033.triad.res.rr.com) 04.37.11 *** Saving seen data "./dancer.seen" 04.47.02 Quit TheSeven (Disconnected by services) 04.47.24 Join [7] [0] (~TheSeven@rockbox/developer/TheSeven) 05.07.12 Quit passstab (Remote host closed the connection) 05.09.17 Join Rob2223 [0] (~Miranda@p5B025539.dip.t-dialin.net) 05.10.14 Quit factor (Quit: Leaving) 05.12.44 Quit Rob2222 (Ping timeout: 252 seconds) 05.17.20 Quit anewuser_ (Read error: Connection reset by peer) 05.40.05 Quit Niteshade (Quit: suck my revolutionary cock) 05.56.50 Join BHSPitMonkey [0] (~stephen@unaffiliated/bhspitmonkey) 06.04.14 Quit prof_wolfff (Ping timeout: 246 seconds) 06.17.10 Join prof_wolfff [0] (~prof_wolf@81.61.201.173.dyn.user.ono.com) 06.29.47 Quit prof_wolfff (Ping timeout: 246 seconds) 06.37.12 *** Saving seen data "./dancer.seen" 06.39.43 Quit enthdegree (Quit: BitchX. A modern, lightweight IRC client.) 06.43.35 Join kevku [0] (x@2001:470:28:773::) 06.49.44 Quit Topy44 (Ping timeout: 246 seconds) 06.52.38 Join Topy44 [0] (Topy44@f049100237.adsl.alicedsl.de) 07.07.54 Join Llorean [0] (~DarkkOne@rockbox/user/Llorean) 07.22.00 # <[Saint]> Hmmmm... 07.22.31 # <[Saint]> Anybody gots some kickin' skillz, yo? 07.39.31 Join robin0800 [0] (~robin0800@genkt-056-222.t-mobile.co.uk) 07.53.43 Join perrikwp_ [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 07.54.44 Quit [7] (Disconnected by services) 07.55.26 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 07.55.27 # * Mir waves at [Saint] 07.56.21 Quit perrikwp (Ping timeout: 248 seconds) 07.58.44 # * [Saint] feels some waves, and dismisses the motion. 08.19.01 # hehe 08.19.13 # well gnite 08.21.29 Quit wtachi (Quit: &) 08.37.14 *** Saving seen data "./dancer.seen" 09.04.08 Quit BHSPitMonkey (Remote host closed the connection) 09.15.14 Quit curtism (Quit: Live Long and Prosper) 09.23.47 Join stoffel [0] (~quassel@pD9E42F7B.dip.t-dialin.net) 09.41.34 Join factor [0] (~factor@r74-195-184-248.msk1cmtc01.mskgok.ok.dh.suddenlink.net) 09.47.20 Quit OzzieJacks (Ping timeout: 255 seconds) 09.49.22 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 09.57.14 Join jdgord [0] (~jdgord@rockbox/developer/JdGordon) 09.57.21 Quit kadoban (Read error: Connection timed out) 09.57.41 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 10.01.33 Join Lear [0] (chatzilla@rockbox/developer/lear) 10.02.26 # Anyone building for Android using Cygwin? 10.03.23 Join pamaury [0] (~quassel@vit94-1-82-67-248-70.fbx.proxad.net) 10.03.23 Quit pamaury (Changing host) 10.03.23 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 10.04.12 # <[Saint]> Lear: no one sane... 10.04.19 # <[Saint]> ;) 10.04.55 # Well, I gave it a quick try, but I didn't come very far... 10.05.47 # <[Saint]> thats because you picked a VERY obscure OS 10.06.05 # <[Saint]> try 'real' linux. 10.07.14 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 10.07.14 Quit bertrik (Changing host) 10.07.14 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 10.08.16 # Seems like the NDK compiler doesn't like Cygwin paths... 10.10.07 # <[Saint]> why cygwin, may I ask? 10.10.43 # <[Saint]> a virtual machine will be WAY fastr. 10.10.47 # You mean version, or what? 1.5 is really old now, so 1.7. 10.11.01 # <[Saint]> ....and, it'll work too. 10.11.07 # But it is nicer to work in the "native" environment... 10.11.56 # <[Saint]> no...i meant "why cygwin, period?" 10.12.24 # Ah, read that as "which Cygwin", not why. :) 10.12.36 # <[Saint]> use a VM, save yourself the grief. 10.13.21 # I started out with Cygwin, and that has worked well enough so far. A VM wasn't really an option when I started. 10.14.11 # <[Saint]> i assure you it was. unless you started ~10 years ago. 10.15.15 # Which is what I did. First contributions where sometime in 2002... 10.15.53 # <[Saint]> and youve used cygwin since? 10.16.07 # <[Saint]> ....poor guy. 10.17.12 # <[Saint]> you could setup a vm in the time it takes a compile to finish using cygwin ;) 10.18.43 # No, it isn't *that* slow... 10.19.32 # <[Saint]> it really is... 10.19.33 Quit rudi_s (Ping timeout: 260 seconds) 10.19.39 Join rudi_s [0] (~simon@austria125.server4you.de) 10.24.00 # Lear: I tried it some time ago. I even have some patch floating around to fix some issue with configure IIRC 10.24.21 # however, I gave up before everything worked. 10.24.56 # Yes, I got past configure. 10.25.12 # then things break :) 10.25.31 # at least that's pretty much where I stopped -- building on Linux is simply way easier and faster 10.26.39 # <[Saint]> amen...and, i was a cygwin advocate, 10.27.24 # either way, if you are bound to using Cygwin you have to fix things -- I'm pretty sure nobody fixed that, and nobody cared (until now) 10.28.19 # <[Saint]> someone cared...but that guy moved to linux ;) 10.28.49 Join lovasoa [0] (~lovasoa@cac94-9-88-162-232-8.fbx.proxad.net) 10.29.21 # someone? As in you? 10.29.40 Quit lovasoa (Remote host closed the connection) 10.30.00 # is there a way to check a rockbox translation manually? (other than through themes.rockbox.org) 10.30.28 # I mean other than translate.rockbox.org 10.30.36 # <[Saint]> nah...the guy that dropped the cygwin/android patch(es) on fs 10.30.37 # as in use it in a sim? 10.36.37 Quit robin0800 (Ping timeout: 252 seconds) 10.37.16 *** Saving seen data "./dancer.seen" 10.41.27 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 10.43.42 # * bertrik doesn't really know what to do about fs#12610 10.43.44 # http://www.rockbox.org/tracker/task/12610 3Clip+ Ticking Noise Fixed in Radio (patches, unconfirmed) 10.44.07 # apparently the hardware design of this tuner is just very sensitive to interference 10.44.43 Join ender` [0] (~ender@foo.eternallybored.org) 10.46.33 Join robin0800 [0] (~robin0800@genkt-058-224.t-mobile.co.uk) 10.46.46 # my best chance so far is that we disable the RSSI feature for the RDA5802 tuner and avoid polling the tuner by using the dedicated stereo-indicator line (if that's even connected) 10.50.38 # perhaps polling at a lower rate would help? 10.53.34 # hm that would still causes interference, but at a lower rate I guess :) 10.55.21 Join evilnick [0] (~evilnick@rockbox/staff/evilnick) 10.58.17 # I guess readout uses i2c? Reading slower would help too, I think 10.58.31 # amiconn, you mean slowing the i2c bus speed? 10.58.41 # Slower as in lowering the i2c transfer speed 10.59.27 # The iriver remote anti-ticking measures work in a similar way 11.00.45 # Either lower the i2c clock, or introduce pauses between the bytes 11.02.41 # I'll try that, say reduce the frequency by 10 or so 11.02.58 # It's a bit-banged i2c implementation, so I don't know the i2c speed exactly 11.03.48 # I'm also still wondering if there's perhaps a bug in the i2c implementation, causing brief short-cuts on the bus 11.06.52 # A bit-bang driver has additional options for lowering interference (spread spectrum method) 11.08.45 # lowering the i2c bus speed indeed seems to help 11.09.32 Quit Lear (Quit: ChatZilla 0.9.88.1 [Firefox 11.0/20120308162450]) 11.09.38 # it's a bit tricky to determine the difference, the noticeability of the ticking depends on signal strength and the material played 11.10.15 # * amiconn wonders why those newer SoCs still need bit-banged i2c 11.10.58 # I think it's just unfortunate design decisions 11.11.44 # there is a hardware i2c bus with the analog codec on it, but somehow the radio has its own i2c bus 11.11.52 # (and addresses are non-conflicting) 11.18.57 # amiconn, how would you implement spread spectrum? and has this been used in rockbox before? 11.21.35 # like, add "random" time to the already existing delays? 11.42.16 Quit Keripo (Quit: Leaving.) 11.58.33 Quit bertrik (Remote host closed the connection) 11.59.27 Join Lear [0] (chatzilla@rockbox/developer/lear) 12.06.59 Quit robin0800 (Ping timeout: 265 seconds) 12.13.57 Quit mystica555_ (Ping timeout: 248 seconds) 12.18.02 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 12.18.02 Quit bertrik (Changing host) 12.18.02 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 12.29.06 Quit stoffel (Ping timeout: 244 seconds) 12.30.13 Join TheLemonMan [0] (~LemonBoy@adsl-ull-226-218.50-151.net24.it) 12.31.35 Join fyre^OS [0] (~nnscript@cpe-68-173-235-85.nyc.res.rr.com) 12.33.30 # bertrik: perhaps it's related to some interference 12.34.10 # some radios chips don't like i2c bus action while tuning for example 12.34.43 Quit fyrestorm (Ping timeout: 252 seconds) 12.35.02 # pamaury, yes, it's most likely interference from the i2c activity 12.35.39 # the display also produces interference, but that goes away after the "backlight" timeout 12.36.09 Join AlexP [0] (~alex@rockbox/staff/AlexP) 12.37.18 *** Saving seen data "./dancer.seen" 12.37.28 # Is it known that peakmeters don't work in a sbs? 12.39.42 # pamaury, regarding the use of gmtime/mktime in RTC drivers, I want to wait until the end of freeze, and then also do each driver separately instead of doing them all at once 12.41.27 # jhMikeS might have some ideas to make gmtime smarter/faster 12.43.14 # ok 12.43.15 # gevaerts: I don't get skinned lists at all, the description on the wiki is hugely confusing IMO 12.43.31 # AlexP: basically you mark a viewport (or a bunch of them with shared label) with %Lb. That viewport will be drawn several times with shifted x and y coordinates, once for each item the list has to draw 12.43.48 # How do you specifiy the coordinates? 12.44.03 # i.e. the original ones and how they shift? 12.45.02 # The %Lb width and height tell the system how big your items will be 12.45.15 # Each line, or image, or whatever? 12.45.36 Join bertrik_ [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 12.45.36 Quit bertrik_ (Changing host) 12.45.36 Join bertrik_ [0] (~bertrik@rockbox/developer/bertrik) 12.45.42 # Then the system adds the %Vi x and y to your list item viewport x and y and draws it as the first item 12.46.03 Quit bertrik (Ping timeout: 255 seconds) 12.46.10 # Then the system adds the %Vi x and y to your list item viewport x and y, and adds the %Lb height to y, and draws it as the second item 12.46.16 # (this is actually a loop :) 12.46.48 # And it does this until it runs out of space in the %Vi? 12.46.52 # yes 12.47.02 # The same goes for x if you enable tiling 12.47.43 # OK, I think 12.48.42 # <[Saint]> AlexP: youre not alone ;) 12.48.44 # And current item refers to the item being drawn in that viewport, i.e. the second time around %LT will give you the text for the second item in the list? 12.48.45 # So basically the viewport coordinates for viewport items are drawn relatively to the list item with (0,0) as their top left hand corner 12.48.53 # yes 12.48.56 Join prof_wolfff [0] (~prof_wolf@81.61.201.173.dyn.user.ono.com) 12.49.24 # gevaerts: So what about if for the main menu you want a small ui viewport area, but a bigger one for e.g. the file list? 12.50.06 # <[Saint]> its a hugely convoluted system, good for very few (basically just "fancy, weird lists) things. 12.50.11 # I'm going to have to have a play and if I get it try to write a better description :) 12.50.22 # Then you'll need to make several labeled %Vi() viewports and conditionally (with %cs) pick one using %VI 12.50.27 # As I spent ages yesterday, and just couldn't make sense of it 12.50.29 # <[Saint]> good luck! 12.50.36 # gevaerts: right 12.50.37 # [Saint]: it's not *that* convoluted! 12.50.42 # <[Saint]> i gave up... 12.50.43 Join anewuser [0] (~anewuser@190.207.136.156) 12.50.43 Quit anewuser (Changing host) 12.50.43 Join anewuser [0] (~anewuser@unaffiliated/anewuser) 12.50.54 # It does make a bit more sense now, but what gevaerts has just described isn't on the wiki :) 12.51.01 # Or not in an understandable way :) 12.51.12 # AlexP: *don't* look at the Wavy theme to try to understand it :) 12.51.22 # OK, I won't :) 12.51.41 # gevaerts: Follow up, do you know anything about peak meters not working in a sbs? 12.52.15 # no. I know they work on a wps, but I never tried on a sbs 12.52.22 # I have :) 12.52.28 # And they don't :) 12.53.04 # Maybe (I have no idea, just a vague guess...) the sbs doesn't do fast refresh tags? 12.53.17 # Ah, possible 12.53.23 # That'd be annoying 12.53.39 # But heh 12.54.18 # <[Saint]> I believe that's deliberate. 12.54.25 Join robin0800 [0] (~robin0800@149.254.60.34) 12.54.36 # <[Saint]> or...."not-implemented" rather than deliberate. 12.54.49 # <[Saint]> only the wps refreshes fast enough for them to be useful. 12.54.52 # AlexP: there's a good chance I think that nano2g USB won't be release-ready within a week (funman wants to look into it and he expects it not to take too long to fix, but as far as I know no attempts at getting a nano2 to him have succeeded yet) 12.54.56 # <[Saint]> but, that may not be the case now. 12.55.22 # So do we extend the freeze, or do we branch as planned and then if needed extend the branch time? 12.55.30 # <[Saint]> fwiw, there's other crazy things you can't do in the sbs too...like seeking. 12.55.35 # <[Saint]> so it may just be oversight. 12.55.44 # <[Saint]> but I believe its refresh rate related. 12.57.38 # gevaerts: Is that the only blocker? 12.58.23 # It's the only one I can think of right now. We should go over the tracker to make sure 12.58.56 # hmmm, did we do anything about translations too? 12.59.09 # No. we have a problem there 12.59.24 # oh, with the site? 12.59.41 # I went over the translations on FS, and about all of them have discussions and comments about "please change X" 13.00.00 # And the site hasn't moved to git yet, so it's two months out of date 13.00.35 # ah 13.00.36 # is there a way to manually check the completeness of a translation? 13.00.37 # OK 13.01.36 # What I think the best approach is is to launch a call for translations as soon as it's fixed and release 3.11.1 soon after that 13.01.48 # OK 13.01.53 Quit robin0800 (Ping timeout: 244 seconds) 13.02.13 # So, we delay for translations and nano 2g usb, the decision is to whether to branch or not 13.02.48 # Well, I wouldn't delay for translations. Missing them is no fun, but it's not a blocker IMO 13.02.56 # On one hand it becomes harder to sync if we branch, but if we do it frees up trunk and are there going to be that many bug fixes in the next week or two? 13.03.07 # Ah, I missed your .1 13.03.10 # The nano2g needing a hard reset most of the time after (or before) a USB connection is 13.03.24 # OK, depends how long nano2g takes 13.04.22 # nano2g is likely to be an isolated fix in an area noone else is touching, so it should be a trivial merge 13.04.34 # yep 13.04.56 # So that can be easily done after we release the wild animals on to master again 13.05.22 # right, right, git = master :) 13.05.32 Join lebellium [0] (~chatzilla@g231190100.adsl.alicedsl.de) 13.05.46 # Yes, git is actually a fork of svn where they just renamed everything :) 13.06.17 # It might be a good idea to grab Torne for when we branch :) 13.06.32 # Definitely. I have no idea how to do it on my own! 13.06.40 # Me neither 13.08.51 Nick bertrik_ is now known as bertrik (~bertrik@rockbox/developer/bertrik) 13.16.53 Join robin0800 [0] (~robin0800@149.254.49.217) 13.18.43 # AlexP: the sbs has a limited update rate. peakmeter needs a faster one 13.18.57 # so yes, it's a known issue and intended 13.19.10 # kugel: I take it that it is limited for a reason? 13.19.40 Join wodz [0] (~wodz@89-76-160-35.dynamic.chello.pl) 13.20.04 # Zagor, Bagder: can you update frontpage please? 13.22.38 # git br v3.11 && git push origin v3.11? 13.22.57 Quit robin0800 (Ping timeout: 245 seconds) 13.23.39 # AlexP: yes, to not cripple list drawing with complicated SBSes 13.23.46 # I made interesting discovery yesterday. It is possible to run ARM core and AHB with the same frequency on rk27xx. The trick is that datasheet doesn't mention how the base clock is derived from pll. If you select arm:ahb = 1:1 it takes both arm and ahb clock from pll/2 if you select arm:ahb = 2:1 it takes arm from pll directly and ahb from pll/2 13.24.09 Quit bertrik (Read error: Connection reset by peer) 13.24.14 # kugel: OK, a shame but if that's the way it is, then c'est la vie :) 13.24.32 Quit evilnick (Ping timeout: 246 seconds) 13.25.23 # I think browsing lists would be no fun with a peakmeter keeping the system busy 13.25.32 # gevaerts: So I have my %Vi and %Lb, what else do I need? 13.25.45 # kugel: I believe you :) 13.25.53 # but things can be changed if you want it hard enough, it's an artificual limited 13.25.59 # -ed 13.26.08 # It is a shame that it isn't doable, but if it kills lists then fair enough :) 13.26.51 # AlexP: well, one (or more if you feel like it) viewport with the label you tell %Lb to use 13.27.28 # Peakmeters also kill battery 13.27.32 # ah right, I got confused again :) 13.29.38 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 13.29.39 Quit bertrik (Changing host) 13.29.39 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 13.35.33 Quit kadoban (Ping timeout: 245 seconds) 13.38.07 # wodz: for making the hd300 show up in Rockbox Utility the status=disabled line needs to get removed from rbutil.ini 13.38.36 # though if installation is working with Rockbox Utility I don't see why that hasn't been done before -- it's not related to a target being marked as stable 13.38.59 # but people can always use the "show disabled target" option to use it. 13.39.52 # bluebrother: should I change this line or you will do it? 13.40.24 Join shanttu [0] (~shanttu@dsl-hkibrasgw3-ffdec300-4.dhcp.inet.fi) 13.41.01 # wodz: I don't care -- I can do that if you want to. 13.43.59 # bluebrother: If you could would be great. I can't commit right now. 13.44.23 # ok, will do that 13.44.47 # is that for the hd300 only or also the hd200? 13.45.02 # HD300 13.45.09 # ok 13.45.30 # hd200 has incomplete manual and is generally less tested as my unit has broken usb bridge 13.45.33 # any reason why the hd200 is disabled in Rockbox Utility? If installation is working fine then there is no reason to keep it disabled 13.45.38 # ok. 13.45.56 # then I'll enable the hd200 as well. The port status is retrieved from the server, so it's different 13.47.36 Join robin0800 [0] (~robin0800@149.254.61.232) 14.00.04 Quit robin0800 (Quit: Leaving) 14.00.30 Join robin0800 [0] (~robin0800@149.254.61.232) 14.03.09 Quit wodz (Quit: Leaving) 14.04.06 Join stoffel [0] (~quassel@pD9E42F7B.dip.t-dialin.net) 14.04.55 Quit jdgord (Ping timeout: 265 seconds) 14.05.57 Quit robin0800 (Ping timeout: 244 seconds) 14.19.35 # bertrik: Yes, essentially it means varying the delays randomly. You don't need high quality randomness, simple linear congruency should do 14.20.20 # It may or may not work better than just lowering the clock, or pausing between bytes. This needs experimentation 14.22.28 # I tried spread spectrum when trying to improve the iriver remote anti-ticking measures. While the first implementation did reduce the ticking, it lowered the update speed too much. After all it's a tradeoff 14.24.30 # Err, that's probably slightly confusing. Spread spectrum was not the first implementation. It's one of the alternatives I tried for the too slow first implementation. It turned out that introducing pauses between bytes worked better than that 14.29.09 # ok thanks, reducing the i2c bus speed already seems to help a lot 14.34.28 Quit stoffel (Ping timeout: 260 seconds) 14.37.21 *** Saving seen data "./dancer.seen" 14.38.46 # gevaerts: If I want two viewports to be displayed for each item but each with different sizes, do I have two %Lb with different labels? 14.44.42 Join mortalis [0] (~mortalis@77.108.98.176) 14.48.04 # AlexP: no, just one Lb, and the same label on all viewports 14.48.18 # gevaerts: But the Lb specifies the size, no? 14.48.50 # Or do I set the Lb width/height to be the same as my largest viewport? 14.49.57 # no, the Lb specifies the used area, not the size of individual viewports 14.50.18 # So the total that is used by all the viewports I specify? 14.51.05 # So e.g. I want one that is 100px high, then a gap of 20px, then another that is 40px high I set Lb height to be 160px? 14.51.17 # yes 14.51.26 # right, OK :) 14.52.32 # You can specify more, and you'll get gaps 14.57.52 Join wtachi [0] (~wtachi@cpe-069-134-168-033.nc.res.rr.com) 15.11.58 # aha, the first bit is working! 15.14.18 # Yay! :) 15.15.09 Join robin0800 [0] (~quassel@149.254.61.160) 15.16.55 # Hm, is VirtualBox not a good "Rockbox VM"? I can't seem to build much faster than in Cygwin with it... (Haven't tested all possible core counts for the VM; 2 was much faster than 4 at least.) 15.19.52 # and then next bit! 15.20.22 # I don't suppose the skin engine can scale images? If I want different sizes I guess I need to provide them all myself? 15.20.38 Join stoffel [0] (~quassel@pD9E42F7B.dip.t-dialin.net) 15.21.08 Join y4n [0] (~y4n@unaffiliated/y4ndexx) 15.21.19 # <[Saint]> it can, for aa, but thats all. 15.21.25 # AlexP: when you're revising the documentation for this, maybe you can clarify the viewport documentation too? I don't think the fact that viewports can share a label and then be displayed by a single %Vd or %Lb call is very clear 15.21.32 # well yeah, I was excluding aa 15.21.48 # gevaerts: I need to finish understanding it first :) 15.21.52 # But yeah :) 15.23.04 # <[Saint]> pfffffft! since when do people understand things before writing docs? 15.23.12 # <[Saint]> ...shameful. 15.23.15 # <[Saint]> ;) 15.24.45 # hrm i have the svn repo with lots of changes done, how can i convert it to git ? 15.25.23 # <[Saint]> diff, checkout, apply diff? 15.26.34 # i expect lots of manual merging :< 15.28.12 # <[Saint]> theres no "git --make_svn_repo_git_repo" unfortunately. 15.31.26 # i'd blame the rb team for having used svn till now 15.31.39 Quit mortalis (Quit: KVIrc 4.1.1 Equilibrium http://www.kvirc.net/) 15.33.43 # TheLemonMan: checkout the same commit in git which your svn copy is at. then it applies cleanly and you can use git to update to a recent version 15.33.51 Quit robin0800 (Ping timeout: 265 seconds) 15.34.53 # "git log --grep=@NNNNN --oneline" gives you the corresponding git commit 15.36.27 Join robin0800 [0] (~quassel@149.254.60.32) 15.36.40 # * [Saint] forgot to mention that, 15.36.48 # <[Saint]> thanks kugel 15.40.17 # the server doesnt look that fast D: 15.40.59 # <[Saint]> initial checkout is kinda slow. 15.41.14 # <[Saint]> but still faster than svn. 15.41.44 # TheLemonMan: no manual merging needed if you're clever 15.41.54 # Ah, kugel already said that :) 15.46.25 # JdGordon: do you already have some time for my bug or are you still busy? :) 15.51.12 Quit Lear (Quit: ChatZilla 0.9.88.1 [Firefox 11.0/20120308162450]) 15.53.33 Join robin0800_ [0] (~quassel@genkt-049-223.t-mobile.co.uk) 15.53.45 Quit robin0800 (Ping timeout: 255 seconds) 15.59.09 Join randumbum [0] (~IRCclient@c-71-193-176-198.hsd1.wa.comcast.net) 16.12.06 # It seems there is a bit of a bug with skinned lists - I have a skinned main menu only, and if I got into a submenu (or files or whatever) and let a long line strat scrolling, when I come back out into the main menu the scrolling line remains overlaid on the skinned main menu 16.12.11 Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) 16.12.15 # It doesn't happen if the line doesn't scroll 16.18.00 # i think it's not limited to skinned lists. I've had this happen in normal cabbiev2 too, but not easy to reproduce 16.18.30 # ah, I've not seem it before but I get it everytime now 16.18.42 # Let me go back to cabbie and see 16.19.07 # in cabbie it happens when going from wps to main menu (IF it happens) 16.19.29 # most of the time there's no problem at all 16.19.33 # ah, here it is litterally pop into a submenu and back 16.19.39 # Or to files or whatever 16.19.43 # And I get it everytime 16.20.14 # It might well be how this sbs is written, as it is the result of me trying to work out skinned lists 16.20.27 # So I might have been supposed to do it another way 16.20.36 # But either way I don't think it should happen 16.28.03 # i agree 16.31.23 Quit lembas (Quit: brb) 16.32.57 Join lembas [0] (~lembas@lembas.ws) 16.36.48 Join passstab [0] (~v@c-68-80-37-73.hsd1.pa.comcast.net) 16.37.10 Quit lembas (Client Quit) 16.37.23 Join lembas [0] (iam@lembas.ws) 16.37.24 *** Saving seen data "./dancer.seen" 16.38.16 Join Ray072 [0] (~Ray072@75-134-123-215.dhcp.aldl.mi.charter.com) 16.39.16 Part Ray072 16.46.18 Quit robin0800_ (Ping timeout: 264 seconds) 16.47.14 Quit guymann (Quit: Lost terminal) 16.47.59 Join guymann [0] (~charles@64-252-120-203.adsl.snet.net) 16.48.50 Join robin0800 [0] (~quassel@genkt-049-224.t-mobile.co.uk) 16.56.29 Join robin0800_ [0] (~quassel@149.254.61.38) 16.57.59 Quit robin0800 (Ping timeout: 252 seconds) 17.01.04 Join robin0800 [0] (~quassel@149.254.61.232) 17.02.06 Quit robin0800_ (Ping timeout: 260 seconds) 17.04.26 Quit robin0800 (Read error: Connection reset by peer) 17.05.09 Join robin0800 [0] (~quassel@149.254.61.161) 17.12.33 # gevaerts: Thanks for the help earlier, I think I got the hang of it 17.13.22 # gevaerts: Now this is not held up as an example of great design, but of me playing with skinned lists (little video of it): http://www.sendspace.com/file/koshqu :) 17.14.45 Quit kevku (Quit: KVIrc 4.0.4 Insomnia http://www.kvirc.net/) 17.15.07 Join CaptainKewl [0] (captainkew@207-237-110-248.c3-0.nyr-ubr2.nyr.ny.cable.rcn.com) 17.18.06 Quit factor (Ping timeout: 252 seconds) 17.19.15 # AlexP: awesome 17.19.27 # hehe :) 17.20.04 # you need prettier images, though (anti-aliased) 17.20.06 # :p 17.20.23 # but that isn't rockbox anyway is it? ;) 17.20.34 # yeah, those are all jaggedy and that :) 17.21.53 # you can fix that with transparent images 17.22.20 # proper transparency, not the pink thing? 17.22.54 # yea 17.22.58 # oh, nice 17.23.06 # I didn't know we supported that :) 17.24.07 # that was my suspicion ;) 17.26.42 Quit robin0800 (Ping timeout: 244 seconds) 17.30.35 Join XavierGr [0] (XavierGr@rockbox/staff/XavierGr) 17.45.15 # kugel: There you go: http://www.sendspace.com/file/48kab7 :) 17.45.59 Join robin0800 [0] (~quassel@149.254.60.163) 17.46.56 # sweet 17.49.19 Join factor [0] (~factor@r74-195-184-248.msk1cmtc01.mskgok.ok.dh.suddenlink.net) 17.51.59 # dfkt: I'm going to use your 7px icons (I just modified a bit the borders) for the next version of my theme. How am I supposed to give you credits? 17.52.30 # by baking me a cake? :) 17.52.47 # ahaha :) 17.53.03 # if you knew how bad cooker I am.... 17.53.03 # * kugel would prefer a beer 17.53.08 # i saw your post in the thread - you can have my PSD files with separate layers of the icons - you just have to resize them and make the black matte white 17.53.19 # that is, if you use photoshop 17.53.29 # gimp can handle psd 17.53.36 # actually I edited your bmp in photoshop and that works fine too :) 17.53.56 Quit Llorean (Read error: Connection reset by peer) 17.54.10 # ah ok... the matte is just a lazy trick to bypass alpha transparency tweaks (which would take a *lot* of work after resizing) 17.54.37 # yes I know.... 17.55.04 # that's why the easiest for me is to edit your bmp and just make the borders less dark sometimes 17.55.10 # yeh 17.55.49 # whhich alpha transparency tweaks? 17.56.17 # resizing messes up the borders, ff00ff becoimes jagged and ugly 17.56.29 Quit Topy44 (Ping timeout: 246 seconds) 17.56.31 # I noticed that too :D 17.56.43 # * kugel repeats that this isn't necessary anymore as rockbox supports true alpha transparency now :) 17.57.00 # he reworked his icons before I guess 17.57.21 # yeh, but that's a lot of work. the source icons are single layer bmps, with ff00ff background, not transparency 17.57.56 # one could probably collect the original icons and rebuild the image strip with real transparency... but matting them was less work ;) 17.58.17 # in gimp it's easy to convert ff00ff to transparency. then you can scale just fine 17.58.43 # oh and actually I never understood when are the viewers icons used?! 17.58.57 # "open with..." menu 17.58.58 # i did remove ff00ff in photoshop, making it transparent, but the borders still were jagged 17.59.31 # i had to copy the free transparent icon layer and put a layer with the same borders, but black filling under them to look good 18.00.02 # i.e. to remove all purple/magenta traces from the borders 18.00.17 # that is after scaling? 18.00.23 # yes 18.00.46 # I'm suggesting to ff00ff->transparency *before* scaling 18.01.06 # trust me, i tried a lot of approaches, none were clean ;) 18.02.03 # I'm just letting you know that you can stop messing with ff00ff now as rockbox supports true transparency with alpha channel now :) 18.02.52 # which goes back to what i said above - working with a source that is a single layer bmp with ff00ff is not as convenient as working on the real transparent deal 18.02.57 Quit robin0800 (Ping timeout: 246 seconds) 18.03.00 # it's a cheap hack, but it works well for one backdrop color - maybe some day i hunt down the single png/svg/ico files and make it properly 18.03.21 # but since all my themes will only ever have black backgrounds, i'm fine with what i have ;) 18.06.53 # pamaury, this is what I intend the imx233 rtc driver to look like once gmtime is in: http://pastebin.com/v5JenQXW 18.07.23 Join curtism [0] (~curtis@bas11-montreal02-1128531121.dsl.bell.ca) 18.07.23 Quit curtism (Changing host) 18.07.23 Join curtism [0] (~curtis@unaffiliated/programble) 18.08.52 Join Topy44 [0] (Topy44@f048201188.adsl.alicedsl.de) 18.11.30 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 18.13.12 Quit Torne (Read error: Connection reset by peer) 18.13.43 Join Torne [0] (~torne@rockbox/developer/Torne) 18.15.11 Quit bluebrother (Disconnected by services) 18.15.11 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother) 18.16.38 Join robin0800 [0] (~quassel@149.254.61.35) 18.18.39 Quit fs-bluebot (Ping timeout: 260 seconds) 18.19.54 Join fs-bluebot [0] (~fs-bluebo@g225255145.adsl.alicedsl.de) 18.20.05 # ok, anyone interested in trying rpms for Fedora for our compilers? 18.20.25 # in case, there's arm-elf-eabi, mips-elf and m68k-elf available: /usr/include/bits/fcntl2.h:51:24: error: call to '__open_missing_mode' declared with attribute error: open with O_CREAT in second argument needs 3 arguments 18.20.35 # ah crap, wrong line pasted 18.20.39 # http://www.alice-dsl.net/dominik.riebeling/rockbox/gcc/ 18.20.55 # you can use that as yum repo 18.21.03 # sh-elf is currently broken. 18.21.43 # there's also no meta package for pulling all other packages required for building Rockbox (yet) 18.21.56 Join Thra11 [0] (~thrall@107.63.125.91.dyn.plus.net) 18.22.03 # packages should work on F14 and up, though they are built on F14 18.35.39 Quit robin0800 (Read error: Connection reset by peer) 18.36.51 Join skx` [0] (~skx@78-22-77-137.access.telenet.be) 18.37.26 *** Saving seen data "./dancer.seen" 18.41.02 # I haven't been able to build sh for a long time 18.41.15 # Actually, it is binutils IIRC 18.43.24 Quit skx` (Ping timeout: 244 seconds) 18.43.33 Join skx` [0] (~skx@78-22-77-137.access.telenet.be) 18.50.37 Quit skx` (Ping timeout: 240 seconds) 18.51.49 Join skx` [0] (~skx@78-22-77-137.access.telenet.be) 18.52.56 Quit Rower85 (Read error: Connection reset by peer) 18.54.41 Quit GeekShadow (Changing host) 18.54.41 Join GeekShadow [0] (~antoine@reactos/tester/GeekShadow) 19.00.07 Join alienkid10 [0] (~alienkid@unaffiliated/alienkid10) 19.02.39 # where can I get the actual font adobe-halvetica for free? I want a 17 point version of it for my fuze+ but there isn't one in the font pack. 19.10.26 Quit alienkid10 (Quit: bye) 19.21.13 Quit stoffel (Remote host closed the connection) 19.34.16 Quit passstab (Remote host closed the connection) 19.38.49 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 19.41.30 Quit perrikwp_ (Ping timeout: 264 seconds) 19.48.30 Join OzzieJacks [0] (~OzzieJack@24.246.47.198) 19.48.46 Join Ray072 [0] (~Ray072@75-134-123-215.dhcp.aldl.mi.charter.com) 19.49.02 Quit mshathlonxp () 19.51.50 Part Ray072 20.02.23 # dfkt: was easy but looong. I'm finally done with editing your icons :) 20.32.36 Quit Thra11 (Ping timeout: 248 seconds) 20.37.29 *** Saving seen data "./dancer.seen" 20.39.46 Join Thra11 [0] (~thrall@69.19.113.87.dyn.plus.net) 20.49.26 Quit y4n (Quit: We're fucking 3LN!) 21.01.23 Quit dfkt (Excess Flood) 21.01.38 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 21.05.29 Quit benedikt93 (Ping timeout: 260 seconds) 21.10.50 Join saratoga [0] (980329e4@gateway/web/freenode/ip.152.3.41.228) 21.11.29 # Lear: (for the logs) rather then cygwin I strongly recommend the VBox image I put on the development guide 21.11.42 # on windows you can SMB mount it and then SSH into it from the windows command line 21.12.06 # its thus exactly like running cygwin (can even use windows programming tools) but much, much faster and easier to setup 21.12.36 # plus its ubuntu based so you won't run into weird compatibility issues as often as with cygwin 21.15.02 Quit factor (Quit: Leaving) 21.27.34 Quit CaptainKewl (Quit: ( www.nnscript.com :: NoNameScript 4.22 :: www.esnation.com )) 21.32.03 Join evilnick [0] (~evilnick@rockbox/staff/evilnick) 21.38.50 Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) 21.41.13 # Would someone mind looking over/merging a couple of commits for me http://gerrit.rockbox.org/r/177 , http://gerrit.rockbox.org/r/171 . 21.44.46 # OzzieJacks: I'd say that at least 171 shouldn't go in during the feature freeze. That's scheduled to end sometime later today though, so it's not a major wait 21.46.28 # Torne: do you have some time today to help with branching? 21.48.58 # gevaerts: i thought branching was dead easy 21.49.21 # funman: it probably is 21.51.02 # lebellium, i just downloaded the ubuntu tango icons (yay for 7zip being able to unpack .deb archives on windows) - i will have a look at them, collecting all the relevant ones for rockbox 21.53.23 # gevaerts: which part of branching do you need help with? 21.53.43 # funman: the bit where I have to make sure gerrit handles everything right 21.58.07 # for future patches which target only a branch and not master, right? 21.58.33 # For 3.11 21.58.50 # http://gerrit.googlecode.com/svn/documentation/2.1/project-setup.html#registering_additional_branches 21.59.28 # it seems we must first create branches in git, and then if we want add them to gerrit UI 22.01.16 # * gevaerts nods 22.01.40 # I'd still like to have Torne verify every step before I mess things up though 22.02.23 # good idea 22.02.39 # btw i'm watching my mailbox for the nano2g, i hope it will come tomorrow 22.03.23 # We won't release until that's fixed, but we shouldn't postpone branching for it I think 22.03.42 # People will get impatient and cold if the freeze lasts too long 22.04.44 # yeah it doesn't prevent branching 22.05.17 # It should be an easy merge later on 22.08.00 # gevaerts: Your probably right about 171 though it only affects touch enabled targets and then only if someone explicitly puts that option in their skin so the risk should be low. 177 does contain fixes. 22.09.51 Join MethoS- [0] (~clemens@134.102.106.250) 22.09.56 # OzzieJacks: I agree about 177, but I think it should be reviewed by someone who actually looked at related code, i.e. not me :) 22.10.58 # Commit 727e8aa in rockbox by 03Rafaël Carré: (Author: Bertrik Sikken) Introduce gmtime.c and use it in the AS3514 RTC driver 22.11.01 # grr 22.11.10 # i didn't want to submit the code, only my comments 22.12.10 # especially if i say "but someone else must approve", gerrit. 22.12.28 # * funman 's still confused by the interface 22.12.51 # So you can review a patch as -2 and push it at the same time? Yes, that's interesting... 22.13.16 # dfkt: nice idea :) 22.14.01 # dfkt: you know about the icons/create-icons-from-tango.pl script? 22.14.15 # 727e8aa build result: All green 22.14.43 Join stripwax_ [0] (~Miranda@87-194-34-169.bethere.co.uk) 22.16.38 # tm->tm_wday = ((seconds % WEEK_SECONDS) / DAY_SECONDS + 4) % 7; 22.16.40 # dfkt: what program do you use on windows to work with icons? 22.16.54 # seconds % WEEK_SECONDS is not needed 22.16.54 # funman: jhMikeS had already +2d it, maybe that was enough? 22.17.10 # gevaerts: yes, i just didn't want to take the blame for it :P 22.17.27 # gevaerts, no, didn't know about that - very useful, thanks! 22.17.40 # OzzieJacks, photoshop 22.18.03 # but i don't know if the division will run faster if we used % before 22.19.26 # I've been nearly confused a few time into thinking that "submit" in gerrit means to submit a comment 22.19.56 # Commit d2aafd1 in rockbox by 03Rafaël Carré: gmtime: reduce array size: days in month fit in 8 bits 22.20.19 # funman: I assume those changes are release-safe? 22.21.32 # they don't really matter so we don't need them either 22.22.12 # hum not true, there's some green delta but not for ATA targets though 22.22.52 # and it is that kind of question that i wanted to avoid by not 'submitting' it myself :) 22.23.22 # bertrik: what do you think ? 22.23.24 # I mean, we're in a freeze, so I'd like to minimise changes 22.23.52 # No point in reverting low-risk changes though 22.24.11 # you could also branch before this commit 22.24.12 # the green delta is expected, because some functionality has now been deduplicated 22.24.23 # We could do that, yes 22.24.50 # bertrik: http://gerrit.rockbox.org/r/#/c/178/ 22.25.42 # * bluebrother^ wonders if it would make sense to have the bot recognize gerrit urls as well 22.29.10 # i think it would be nice 22.29.20 # was going to suggest it actually but was afraid someone might ask me to do it 22.31.55 # gevaerts, funman, I wanted to wait with that commit until freeze was over, I think it's reasonably safe (I tested it on three sansas) but didn't want to take the chance 22.33.13 # I prefer to revert the last two commits 22.33.39 # why not simply branch before that commit? 22.35.06 # If we branch soon, yes, that's the best option 22.35.18 # If not I'd say we revert on the branch 22.35.25 # (if needed) 22.35.59 # i'd prefer to branch before and cherry-pick any required changes from master 22.36.35 # Yes, you're right. That's probably the best option 22.36.49 # when was freeze announced? 22.37.00 # A week ago 22.37.14 # Well, a week and 13 minutes 22.37.31 *** Saving seen data "./dancer.seen" 22.37.34 # then it's over since you said the freeze would be a week 22.37.56 # It wasn't over yet when funman accidentally clicked on submit! 22.38.10 # It still had 13 minutes to go then :) 22.38.11 # make an example of him 22.43.14 Quit stripwax_ (Read error: Connection reset by peer) 22.43.47 Quit kadoban (Ping timeout: 245 seconds) 22.44.17 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 22.51.19 Quit TheLemonMan (Quit: WeeChat 0.3.7) 23.15.21 Join passstab [0] (~v@c-68-80-37-73.hsd1.pa.comcast.net) 23.16.15 Join Scromple [0] (~Simon@119.225.209.134) 23.17.31 Quit shanttu (Remote host closed the connection) 23.20.57 # lebellium: this evening I'll have time to look at it 23.22.41 # <[Saint]> Oooop, you've done it now! 23.24.12 # gevaerts: btw for the branch name, git branch -r shows the existing names for older releases branches 23.24.42 Join lebellium_ [0] (~chatzilla@g231190100.adsl.alicedsl.de) 23.26.08 # [Saint]: Just 'cause it's easier to tell you here: the latest theme has no popups when clicking on the album-art 23.26.21 # Volume works as it did before 23.26.27 # http://forums.rockbox.org/index.php/topic,33700 23.26.31 Quit lebellium (Ping timeout: 246 seconds) 23.26.35 # am i just not remembering how fuze+ patching works? 23.26.38 Nick lebellium_ is now known as lebellium (~chatzilla@g231190100.adsl.alicedsl.de) 23.26.52 # <[Saint]> Well...that's a big pile of bums. 23.32.10 Quit skx` (Ping timeout: 252 seconds) 23.32.17 Join skx` [0] (~skx@78-22-77-137.access.telenet.be) 23.32.39 # <[Saint]> what the shit? why? 23.34.08 Quit benedikt93 (Quit: Bye ;)) 23.35.34 Quit skx` (Client Quit) 23.35.38 # gevaerts: hi 23.35.48 # * gevaerts jumps 23.35.58 Quit Scromple (Quit: Leaving) 23.37.04 # <[Saint]> evilnick: 480x800 I assuem? 23.37.10 # <[Saint]> * assume too 23.37.14 # Torne: I'd like to branch v3.11 based on 3448f5b6ad25f59e01ece347cb06e09652915e30. What procedure should I follow? 23.37.15 # Yes, that's the one 23.37.22 # <[Saint]> Hmmmm... 23.37.37 # <[Saint]> I see no good reason (none at all, in fact) why this should be so. 23.37.41 # gevaerts: add yourself to the release group if you haven't already and either push that or just do it in the project web ui 23.37.47 # they both do the same thing 23.38.11 # Ah, you can branch from there! 23.38.21 # yeah, if the commit you want to be the head alreayd exists 23.38.46 # OK, v3.11 now exists apparently! 23.39.11 # yup, that's it 23.39.33 # any committer can use it exactly as with master now 23.39.40 # including pushing to refs/for/v3.11 to submit changes for review 23.40.17 # OK, so the only remaining bit is that I'll have to try to remember how to check out a remote branch :) 23.40.28 # * gevaerts knows he has done this before! 23.40.29 # git checkout -b something origin/v3.11 23.40.36 # if you just do "git checkout v3.11" it will create a local branch that tracks that for you 23.40.51 # it assumes i fyou name a remote branch you want to make a locla tracking branch from it 23.40.56 # Oh, good 23.41.22 # funman: you always want -t when creating local branches from remotes 23.41.36 # but yes, git checkout -b whatever -t origin/v3.11 is the explicit way 23.41.58 # how do you get rid of a patch set that has a problem if it came after a good one? 23.42.16 # Torne: ok 23.42.44 # jhMikeS: grab the old one and push it again 23.44.52 # hmm...I was hoping for some facility to pick which is the one that passes muster 23.48.00 # can we change the front page to show the merge time rather then the commit time for the local repo? 23.48.09 Topic "3.11 has been branched | Please read before speaking: http://www.rockbox.org/wiki/IrcGuidelines | Please direct offtopic/social chat to #rockbox-community | This channel is logged at http://www.rockbox.org/irc" by ChanServ (ChanServ@services.) 23.48.21 # its less interesting to know when someone committed locally then when it joined the git repo 23.49.28 # you mean the commit time, rather than the author time 23.49.38 # (since they are cherrypicks) 23.49.50 # but yes, we probably should 23.50.12 # there is no way to timestamp actually merged commits that way, but since we are currently cherrypicking you can :) 23.50.12 # * [Saint] concludes that if its not broken in current source with 240x320 that he should just go hang himself because shit is seriously f***ed up. 23.50.48 # did you ever figure out a way to have sequential revision numbers? 23.51.28 # er, sorta. i haven't finished the script to do it cleverly 23.51.35 # i had forgotten about it, sorry :) 23.51.54 # getting that in would be nice 23.52.09 # right now its relatively confusing for people to figure out what they're running 23.58.43 Join bitcraft [0] (~bitcraft@173-20-20-92.client.mchsi.com)