--- Log for 01.07.111 Server: hitchcock.freenode.net Channel: #rockbox --- Nick: logbot_ Version: Dancer V4.16 Started: 8 days and 21 hours ago 00.01.43 Quit dantje_ (Quit: Ex-Chat) 00.01.59 Join Thra11_ [0] (~thrall@162.166.pn.adsl.brightview.com) 00.03.01 Quit Thra11 (Ping timeout: 252 seconds) 00.06.13 Quit Buschel (Quit: ChatZilla 0.9.87 [Firefox 3.6.18/20110614230723]) 00.06.25 Quit mudd1 (Quit: Ex-Chat) 00.12.38 Quit krazykit (Ping timeout: 258 seconds) 00.18.11 Quit dfkt (Quit: -= SysReset 2.55=- Sic gorgiamus allos subjectatos nunc.) 00.21.31 *** Saving seen data "./dancer.seen" 00.21.51 Quit Farthen (Read error: Operation timed out) 00.22.06 Join Farthen [0] (~Farthen@static.225.178.40.188.clients.your-server.de) 00.25.50 Quit ender` (Quit: /[,\(\s]?#1(s)(\s+-?\d+(?{}\.\d+)?\s+-?\d+(?{}\.\d+)?\s+-?\d+(?{}\.\d+)?\s+-?\d+(?{}\.\d+)?\s+-?\d+(?{}\.\d+)?\s+-?\d+(?{}\.\d+)?)(\s+-?\d+(?{}\.\d+)?\s+-?\d+(?{}\.\d+)?)+(\)?=|\s|$)/) 00.27.57 Quit alexbobp (Ping timeout: 252 seconds) 15.02.29 *** Started Dancer V4.16 15.02.29 *** Connected to irc.freenode.net on port 6667 15.02.29 *** Logfile for #rockbox started 15.02.29 Mode "logbot :+i" by logbot 15.02.33 *** Server message 501: 'logbot :Unknown MODE flag' 15.02.33 Join logbot [0] (~rockbox@giant.haxx.se) 15.02.33 Join Thra11 [0] (~thrall@13.76.113.87.dyn.plus.net) 15.02.33 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 15.02.33 Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) 15.02.33 Join dan_a [0] (d917a37d@gateway/web/freenode/ip.217.23.163.125) 15.02.33 Join eGen_ [0] (generat0r@gate.mmdecin.cz) 15.02.33 Join dfkt [0] (dfkt@unaffiliated/dfkt) 15.02.33 Join MethoS- [0] (~clemens@134.102.106.250) 15.02.33 Join GeekShadow [0] (~Antoine@reactos/tester/GeekShadow) 15.02.33 Join n1s [0] (~quassel@rockbox/developer/n1s) 15.02.33 Join swilde [0] (~wilde@aktaia.intevation.org) 15.02.33 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 15.02.33 Join quiccker [0] (~quiccker@212.174.109.55) 15.02.33 Join TheLemonMan [0] (~lem0n@ppp-219-30.26-151.libero.it) 15.02.33 Join dionoea [0] (~dionoea@yop.chewa.net) 15.02.33 Join utanapischti [0] (~username@p4FF2D6A6.dip.t-dialin.net) 15.02.33 Join petur [0] (~petur@rockbox/developer/petur) 15.02.33 Join ender` [0] (krneki@foo.eternallybored.org) 15.02.33 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 15.02.33 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 15.02.33 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 15.02.33 Join sideral [0] (~sideral@rockbox/developer/sideral) 15.02.33 Join ReimuHakurei [0] (~reimu@74.112.212.15) 15.02.33 Join FoolOnHill [0] (~foh@adsl-98-71-68-182.bhm.bellsouth.net) 15.02.33 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 15.02.33 Join Topy44 [0] (~Topy44@f049013143.adsl.alicedsl.de) 15.02.33 Join Rob2222 [0] (~Miranda@p4FFF2387.dip.t-dialin.net) 15.02.33 Join Unhelpful [0] (~quassel@rockbox/developer/Unhelpful) 15.02.33 Join pixelma [0] (quassel@rockbox/staff/pixelma) 15.02.33 Join amiconn [0] (quassel@rockbox/developer/amiconn) 15.02.33 Join bthomson [0] (~bthomson@c-68-33-5-232.hsd1.va.comcast.net) 15.02.33 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 15.02.33 Join bzed [0] (~bzed@devel.recluse.de) 15.02.33 Join alexbobp [0] (~alex@108.60.198.56) 15.02.33 Join balintx [0] (~quassel@szerver1.gulyasp-koll.sulinet.hu) 15.02.33 Join FOAD [0] (~dok@83.161.135.61) 15.02.33 Join krazykit [0] (~krazykit@206.183.185.8) 15.02.33 Join Farthen [0] (~Farthen@static.225.178.40.188.clients.your-server.de) 15.02.33 Join freqmod [0] (~fredrik@2001:700:300:1430:226:18ff:fe81:1e24) 15.02.33 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 15.02.33 Join boghog [0] (~aphax@2001:980:34c7:0:1e6f:65ff:fe86:1e03) 15.02.33 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 15.02.33 Join knittl [0] (~knittl@unaffiliated/knittl) 15.02.33 Join simabeis [0] (~simabeis@lobmenschen.de) 15.02.33 Join avacore^ [0] (~avacore@1008ds1-rdo.0.fullrate.dk) 15.02.33 Join zchs [0] (~zchs@ool-44c2aff0.dyn.optonline.net) 15.02.33 Join AlexP [0] (~alex@rockbox/staff/AlexP) 15.02.33 Join n17ikh [0] (~n17ikh@c-174-56-150-44.hsd1.sc.comcast.net) 15.02.33 Join kugel [0] (~kugel@rockbox/developer/kugel) 15.02.33 Join belak [0] (belak@subtle/user/belak) 15.02.33 Join ps-auxw [0] (~arneb@2001:470:c807:0:1532:4e5f:2ad3:4123) 15.02.33 Join Pikel [0] (~xaero@ool-435056c7.dyn.optonline.net) 15.02.33 Join sega01 [0] (~sega01@cpe-70-120-87-173.satx.res.rr.com) 15.02.33 Join Xerion [0] (~xerion@5419A766.cm-5-2c.dynamic.ziggo.nl) 15.02.33 Join factor [0] (~factor@74.197.205.204) 15.02.33 Join mikroflops [0] (~yogurt@h-34-156.A238.priv.bahnhof.se) 15.02.33 Join Llorean [0] (~DarkkOne@rockbox/user/Llorean) 15.02.33 Join ack [0] (~ack@mingbai.org) 15.02.33 Join linuxstb [0] (~linuxstb@rockbox/developer/linuxstb) 15.02.33 Join CIA-14 [0] (~CIA@cia.atheme.org) 15.02.33 Join Zarggg [0] (~zarggg@24.229.139.169.res-cmts.sm.ptd.net) 15.02.33 Join bieber [0] (~quassel@162-78.97-97.tampabay.res.rr.com) 15.02.33 Join [fred] [0] (fred@ircop.efnet.at) 15.02.33 Join jordan` [0] (gromit@2a01:e34:eebf:c890:21a:4dff:fe63:6966) 15.02.33 Join ender| [0] (krneki@foo.eternallybored.org) 15.02.33 Join Xerrao [0] (~XRO@66.228.38.252) 15.02.33 Join GodEater [0] (~bibble@rockbox/staff/GodEater) 15.02.33 Join guymann [0] (~charles@66-159-149-141.adsl.snet.net) 15.02.33 Join simonlnu [0] (gfpg5UNKrx@unaffiliated/simonrvn) 15.02.33 Join JesusChrysler [0] (~JesusChry@c-69-253-15-232.hsd1.pa.comcast.net) 15.02.33 Join Torne [0] (~torne@rockbox/developer/Torne) 15.02.33 Join Guinness [0] (Slayer@c-68-55-111-159.hsd1.va.comcast.net) 15.02.33 Join soap [0] (~soap@rockbox/staff/soap) 15.02.33 Join scorche [0] (~scorche@rockbox/administrator/scorche) 15.02.33 Join bug2000 [0] (~bug@unaffiliated/bug2000) 15.02.33 Join kkit|sh [0] (~kkit@li135-248.members.linode.com) 15.02.33 Join niekie [0] (~niek@CAcert/Assurer/niekie) 15.02.33 Join Vimk [0] (~Vimk@fireslash.net) 15.02.33 Join quem [0] (~foo@c83-254-240-201.bredband.comhem.se) 15.02.33 Join tmzt [0] (~tmzt@adsl-99-164-33-229.dsl.akrnoh.sbcglobal.net) 15.02.33 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 15.02.33 Join advcomp2019 [0] (~advcomp20@unaffiliated/advcomp2019) 15.02.33 Join mystica555_ [0] (~mike@71-208-200-171.hlrn.qwest.net) 15.02.33 Join parafin [0] (parafin@paraf.in) 15.02.33 Join gevaerts [0] (~fg@rockbox/developer/gevaerts) 15.02.33 Join mystica555 [0] (~Mike@71-208-200-171.hlrn.qwest.net) 15.02.33 Join Elfish [0] (amba@2a01:4f8:100:90a1:abc:abc:abc:abc) 15.02.33 Join Hadaka [0] (~naked@naked.iki.fi) 15.02.33 Join gammy [0] (gammy@li274-9.members.linode.com) 15.02.33 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 15.02.33 Join jfc [0] (~john@stat-bng-72-73-80-12.ngn.east.myfairpoint.net) 15.02.33 Join zu [0] (~zu@ks355000.kimsufi.com) 15.02.33 Join ruskie [0] (ruskie@sourcemage/mage/ruskie) 15.02.33 Join Rondom [0] (~rondom@2a01:488:66:1000:b24d:4f2f:0:1) 15.02.33 Join ranmachan [0] (ranma@2a01:4f8:130:9321::2) 15.02.33 Join pjm0616 [0] (~user@114.200.203.101) 15.02.33 Join TBCOOL [0] (~tb@c-3c3671d5.09-42-73746f22.cust.bredbandsbolaget.se) 15.02.33 Join Slasheri [0] (miipekk@rockbox/developer/Slasheri) 15.02.33 Join Zambezi [0] (Zulu@80.67.9.2) 15.02.33 Join B4gder [241] (~daniel@rockbox/developer/bagder) 15.02.33 Join jae [0] (~jae@dedicated.jaerhard.com) 15.02.33 Join rudi_s [0] (~simon@austria125.server4you.de) 15.02.33 Join aevin [0] (eivindsy@unaffiliated/aevin) 15.02.33 Join Espreon [0] (~espreon@wesnoth/developer/espreon) 15.02.33 Join rasher [0] (~rasher@rockbox/developer/rasher) 15.02.33 Join neferty [0] (~andor@173.242.127.201) 15.02.33 Join yosafbridge [0] (~yosafbrid@li125-242.members.linode.com) 15.02.33 Join Barahir [0] (~jonathan@fb08schindler24.anorg.chemie.uni-giessen.de) 15.02.33 Join maraz [0] (maraz@kapsi.fi) 15.02.33 Join preglow [0] (thomj@rockbox/developer/preglow) 15.02.33 Join linuxguy3 [0] (~timj@216-80-116-174.c3-0.lem-ubr1.chi-lem.il.cable.rcn.com) 15.02.33 Join Utchy [0] (~Utchy@rps6752.ovh.net) 15.02.33 Join @ChanServ [0] (ChanServ@services.) 15.02.33 Join desowin [0] (~desowin@atheme/member/desowin) 15.02.33 Join feisar-_ [0] (jljhook@ihq.in) 15.02.33 Join iq [0] (~iq@unaffiliated/iq) 15.02.33 Join Staphylo [0] (staphylo@hyperion.epimeros.org) 15.02.33 Join scorche|sh [0] (~scorche@rockbox/administrator/scorche) 15.02.33 Join ThomasAH [0] (~thomas@aktaia.intevation.org) 15.02.33 Join ved [0] (ved@ddsbox.co.cc) 15.02.33 Join Galois [0] (djao@efnet-math.org) 15.02.33 Join merbanan [0] (~banan@c-83-233-242-251.cust.bredband2.com) 15.03.03 Part quem 15.04.35 # the fuze+ uses SW i2c with HW i2c pins 15.05.20 # (if it helps you) 15.06.25 # site is up 15.06.44 # great 15.14.06 Quit krazykit (Ping timeout: 246 seconds) 15.28.58 Join fdinel [0] (~Miranda@modemcable036.124-131-66.mc.videotron.ca) 15.38.22 # New commit by 03miipekk (r30108): Fixed incorrect dircache reallocation during tagcache commit. 15.41.46 Join patheticbliss [0] (~calvin@75-134-134-13.dhcp.roch.mn.charter.com) 15.43.41 Quit wodz (Ping timeout: 240 seconds) 15.47.01 Join webguest608 [0] (~46abe3c7@giant.haxx.se) 15.47.55 Quit webguest608 (Client Quit) 15.48.29 # New commit by 03miipekk (r30109): Allocate indices directly in ramcache header. Add version code to ... 15.49.05 # the website doesn't display commits 15.49.38 Mode "#rockbox +o B4gder" by ChanServ (ChanServ@services.) 15.49.43 Topic "3.9 released! | 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 | An upgrade caused issues with the wiki. We are on the case" by B4gder (~daniel@rockbox/developer/bagder) 15.49.47 Mode "#rockbox -o B4gder" by ChanServ (ChanServ@services.) 16.01.44 Quit bthomson (Quit: WeeChat 0.3.3-dev) 16.05.27 Join bthomson [0] (~bthomson@c-68-33-5-232.hsd1.va.comcast.net) 16.07.54 Quit petur (Quit: Ex-Chat) 16.15.02 Quit patheticbliss (Ping timeout: 276 seconds) 16.17.04 Quit bthomson (Quit: WeeChat 0.3.3-dev) 16.21.16 Join patheticbliss [0] (~calvin@75-134-134-13.dhcp.roch.mn.charter.com) 16.21.42 Join bthomson [0] (~bthomson@c-68-33-5-232.hsd1.va.comcast.net) 16.22.15 # test builds also don't show up 16.28.47 # r30109 build result: All green 16.30.36 # i assume songdbj in svn is not actually relevant or interesting to anyone any more, since it's not been changed since 2005? I was going to drop the branch for it (the code will still be present in trunk's history, since it was never changed after being split out of trunk) 16.32.24 Quit bthomson (Quit: WeeChat 0.3.3-dev) 16.33.10 Join asper [0] (~5d2b171c@giant.haxx.se) 16.33.15 # hi guys 16.33.41 # I can send an Archos AV500 do some devs if someone is able to understand it and make a port for av500 ! 16.33.47 # is anyone interested ? 16.34.08 Quit sideral (Disconnected by services) 16.34.08 Join sideral1 [0] (~sideral@rockbox/developer/sideral) 16.35.04 Join bthomson [0] (~bthomson@c-68-33-5-232.hsd1.va.comcast.net) 16.35.10 # Torne: sounds good to me 16.35.19 Quit sideral1 (Remote host closed the connection) 16.36.47 Join sideral [0] (~sideral@rockbox/developer/sideral) 16.36.48 # on the other hand, having an archival branch for it also wouldn't hurt 16.37.29 # The code there was last touched in 2005 16.37.36 # Well, if we do want to keep a ref pointing at it, it'd probably be better to point it at the revision of trunk before it was deleted from trunk 16.37.40 # rather than at the split-out branch 16.37.56 # because the split-out branch includes duplicated commits due to being a subtree 16.39.20 # Torne: I'd say drop it 16.39.46 # i'm also dropping the branches for christi, dast, rockbox, zagor 16.39.49 # It seems to be a java tool to interact with our *previous* database 16.39.53 # since they contain no actual code that's different to what's in trunk 16.39.56 # I'm not sure I fully understand this. What extra commits does it have if it was never changed after the split? 16.40.06 # sideral: The things *before* the split have to be duplicated 16.40.15 # because their effective root directory is trunk/songdbj 16.40.17 # instead of trunk 16.40.29 # because in git branches/tags can't be subtrees of their parents 16.40.30 # Ugh. OK, drop it :) 16.41.13 # anyway. the old cvs branches/tags for specific people are all empty of actual changes so i'm killing them and their associated tags 16.41.27 # themes, translate and www will all go into seperate repositories since they share no history with trunk 16.43.05 # so that leaves bootloader_ams_pp, bootloader_ipod, gigabeat-s, mcdtexp, skinenginebreak and the v3_* branches 16.43.18 # i assume everything in gigabeat-s, mcdtexp, and skinenginebreak is actually merged 16.43.31 # and thus they don't really want to be active branch heads? 16.45.00 # sorry to be boring but... is there a reason why no-one port rockbox to archos AVXXX devices ? 16.45.19 # asper: ports are done because people with the skills to do a port are interested 16.45.34 Quit sideral (Remote host closed the connection) 16.45.43 # contributing a device is rarely actually much help since generally if people are sufficiently interested to port to a device they either already have one or are willing to buy one 16.45.46 # though thanks for the offer :) 16.46.05 # ok, sorry for my post :P 16.46.13 # it's okay, we don't mind you offering :) 16.46.30 # just letting you know that it's not very likely someone is interested. they might still be :) 16.46.36 # I tested rockbox with archos recorder, sansa e200 aandroid and fuze 16.46.41 # it is a reallty GREAT software 16.47.06 # oh and also old archos jukeboxe player 16.47.28 # it seems that texas intruments chips are a pain in the ass for developers 16.47.38 # asper: I'd say offers of hardware might be better on the -dev mailing list. 16.47.41 # this may be is the reason why no one port it to av devices 16.47.43 Join sideral [0] (~sideral@rockbox/developer/sideral) 16.47.46 # asper: it also highly depends on the hardware 16.47.51 # ok, sod it, i'll write a proposal for what to do with our (rather large) list of branches and tags and post to the list 16.47.59 # and if nobody objects i am right. ;) 16.48.25 # ..hm 16.48.29 # actually one more questoin 16.48.55 # git generally doesn't distinguish branches and tags, you can use either in most places (and tabcompletion generally matches both) 16.49.12 # thus there is potential confusion if we have a branch called v3.8 and also a tag v3.8 16.49.23 # possibly the branches should be called something different 16.49.30 # suggestions? :) 16.49.36 # v3.8-tag? 16.49.47 # It's nicer to keep the tags named that way 16.49.49 # i think. 16.49.55 # because git describe describes versions with respect to tags 16.49.58 # asper: by curiosity, what is the hardware of this archos ? 16.50.06 # you are talking about a TI chip 16.50.08 # hm, ok 16.50.10 # e.g. git describe will return "v3.8" 16.51.00 # * gevaerts tries thinking about this 16.51.09 # I think AlexP should decide 16.51.17 # heh 16.51.48 # Torne: Presumably a branch called "v3.8" would be working towards a 3.8 release? So call the branch "v3.8-rc" and the tag "v3.8"? 16.52.03 # dan_a: heh. 16.52.10 # That's not a terrible idea, *but*.. 16.52.12 # dan_a: that would be misleading I think 16.52.22 # The branch also goes to 3.8.1 later on 16.52.38 # one other thing I was intending to maybe do, was tag the trunk revision immediately after branching for 3.8 as v3.9pre or similar 16.52.59 # such that describe will describe trunk versions as being v3.9pre-44- 16.53.01 # v3.8-rb (release branch)? 16.53.04 # if there are, say, 44 commits 16.53.14 # which sort of preserves a sequential version number in a reasonably sane way :) 16.53.42 # That could be a good idea 16.53.51 # Yes, I think so 16.54.02 # It will include enough characters of the sha that it is guaranteed to be unique also 16.54.07 # That would actually fix the confusion of people thinking current svn is still some sort of 3.x 16.54.07 # so you can ignore the number if you want 16.54.26 # this is the page i compiled for archopen years ago: http://www.archopen.org/tiki-index.php?page=AV5xx_Chipset 16.54.31 # all the hardware documented 16.55.18 # TMS320DM320 16.55.27 # that seems to be a sort of prototype 16.55.33 # by TI 16.55.40 # gevaerts: i think it's useful. we sort of discussed it at devcon and people were generally not against it 16.55.49 Quit sideral (Remote host closed the connection) 16.55.57 # it's infinitely more useful to nondevelopers than a plain SHA 16.56.04 # * gevaerts nods 16.56.16 # and it's less of a hack than trying to cobble together a sequential number ourselves by reading git log or whatever. 16.56.46 Join sideral [0] (~sideral@rockbox/developer/sideral) 16.56.49 # One thing we lose with git is the easy "modified" marker 16.56.50 # how should i go to create a new rockbox target ? 16.56.55 # gevaerts: describe can also do that 16.57.02 # git describe --dirty 16.57.09 # Torne: yes, but compared to what? 16.57.23 # Well, there is that. 16.57.24 # no datasheet in 2008 16.57.26 # This "distributed" thing gets in the way :) 16.57.28 # Dirty is compared to HEAD 16.57.29 # now I don't know 16.57.48 # There is an alternative way to construct git "versions" which identifies branches 16.57.53 # but it makes uglier looking output 16.58.01 # * Torne finds an example 16.58.17 # asper: I believe we do have some TMS320DM320 code 16.58.56 # TheLemonMan: NewPort on the wiki ? 16.59.10 # thanks :) 17.00.59 # ok, git name-rev is useless because it goes backwards ;) 17.02.30 *** Saving seen data "./dancer.seen" 17.04.40 # so hm this is actually a little hard ;) 17.04.56 # yeah, iirc the half working creative devices use that texas thing 17.05.51 Quit sideral (Disconnected by services) 17.05.52 Join sideral1 [0] (~sideral@rockbox/developer/sideral) 17.06.04 Quit sideral1 (Remote host closed the connection) 17.08.28 Join sideral [0] (~sideral@rockbox/developer/sideral) 17.09.39 Quit Thra11 (Quit: kthxbai) 17.14.59 Nick balintx is now known as nemvagyok (~quassel@szerver1.gulyasp-koll.sulinet.hu) 17.16.19 Quit sideral (Remote host closed the connection) 17.16.58 Join sideral [0] (~sideral@rockbox/developer/sideral) 17.17.36 # gevaerts: okay actually this is significantly less tractable than I thought :) 17.18.23 Nick nemvagyok is now known as balintx (~quassel@szerver1.gulyasp-koll.sulinet.hu) 17.19.06 # gevaerts: symmetry of distributed development kinda screws you. 17.24.58 # Torne: maybe we can plan ahead and say how many revisions are allowed between releases? :) 17.25.11 # heh. 17.25.45 Quit patheticbliss (Ping timeout: 260 seconds) 17.25.54 # so yeah. describe with suitable tags works nicely for describing revisions on our trunk 17.26.04 # but it does not distinguish branches 17.26.34 Quit sideral (Remote host closed the connection) 17.26.47 # and even if you explicitly check what branch you are on that doesn't stop it from describing something as v3.9-44 if it's a commit directly onto someone's local master that's the child of the (common) v3.9-43 17.27.21 # We'll have to learn to look up hashes I guess 17.27.24 Join sideral [0] (~sideral@rockbox/developer/sideral) 17.27.37 # it's semi-tempting to suggest taht we make version.sh spit out only a SHA by default unless given some explicit arg telling it it's doing an "official" build 17.27.43 # not sure :) 17.29.14 # Worth thinking about when we do the build script overhaul 17.29.33 # The downside there is that people doing their own builds will get nonsequential numbers 17.29.39 # even if they've changed nothing 17.29.52 # unless they also do the same thing in which case you are back at not knowing if it's modified or not 17.30.23 # Depends on how it works I guess 17.30.40 # expecting people to tell the difference between v3.9pre-44-g337e922 and v3.9pre-44-gf27028d is maybe tricky 17.30.46 Join patheticbliss [0] (~calvin@75-134-134-13.dhcp.roch.mn.charter.com) 17.30.52 # and even if you spot the difference you would have to go look up which one was "right" :) 17.31.24 # pamaury, how is the gpio direction set ? 17.31.50 # there is no "direction", there is "output enable" 17.32.14 # If we go that way, we might want to consider something like v3.9pre-44-${SOMEIDENTIFIER}-g337e922, so it's not *all* just generated, and we set SOMEIDENTIFIER to "official" (or preferably something shorter...). That would solve the accidental confusion 17.32.27 # you can read any pin whatever the function using DIN, but if you want it out, you must set it to GPIO and enable output to drive it 17.32.30 Quit ender` (Quit: The sardines were packed as tight as the coach section of a 747.) 17.32.36 # gevaerts: That's probably better 17.32.48 # (and then enable/disable pull-up) 17.33.34 # Torne: it would be good if the version string needs less than three minutes to scroll over a Player screen though :) 17.33.34 # Torne: Why not make ${SOMEIDENTIFIER} be the branch name? 17.34.01 # dan_a: because in the "easy" case that may be trunk/master anyway 17.34.10 # i certainly do not bother making a branch for every change I make :) 17.34.30 # it needs to be something not automatic 17.34.35 # huh in the i2c code there's no output enable access 17.34.51 # it's it bit-banging ? 17.34.54 # *is it 17.34.55 # yep 17.35.02 # just so that "builds from the build system" cannot be confused with similar looking builds from elsewhere which may have different sources 17.35.33 # anyway, er 17.35.47 # the one I want to ponder really for now is what we call the branches we prepare releases on :) 17.36.09 # TheLemonMan: perhaps output is enabled by default, see the datasheet 17.36.13 Join ender` [0] (krneki@foo.eternallybored.org) 17.36.23 # Torne: $VERSION-releaseprep? 17.36.31 # other than "not vx.y-pre because we probably want to use that for describe output" 17.37.02 # dan_a: possibly, but brevity is a virtue when some devices have small screens :) 17.37.38 # * dan_a must put Rockbox on his Sansa Clip at some point 17.37.48 # TheLemonMan: are you sure ? I say this because if you implement i2c by bit-banging, the difference between driven and not driven pin is very important 17.38.01 # Torne: maybe use "v3.8" for the branch, and "v3.8-final", "v3.8.1-final" for the release tags? 17.38.15 # hm 17.38.23 # The latter can be long, since we override the version string for those anyway 17.38.36 # Ah, true 17.38.48 # perhaps the ROM enable the output for some reason 17.39.06 Quit sideral (Quit: Leaving.) 17.40.58 # argh, git-- 17.41.54 # i fear the output is set somewhere in the first lines of start 17.42.28 # is that frightening ?:) 17.43.37 # hehe, tons of ldr/str in that part, getting confused is really easy 17.58.51 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.02.34 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 18.03.07 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 18.03.13 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 18.03.42 Quit n1s (Remote host closed the connection) 18.16.17 # Hmm its too quiet to test my change to yaaic :-( 18.16.21 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 18.16.25 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 18.17.10 Join Horscht [0] (~Horscht@xbmc/user/horscht) 18.25.19 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 18.25.56 # kugel: heh 18.26.19 Join sideral [0] (~sideral@rockbox/developer/sideral) 18.26.46 # Torne: have you looked at the bootloader_ipod history to see who to ask for more info about it? :) 18.38.09 # Torne: I think the v3.9-prexx is a fine idea - it is what e.g. quassel does and I also found it simple and useful 18.39.10 Quit dan_a (Ping timeout: 252 seconds) 18.39.32 # as for branches, maybe branch-3.8 or 3.8-branch or something like that? A bit ugly, but... 18.41.07 # AlexP: I actually think I prefer the "v3.8" name for the branch and then "v3.8-final" or "v3.8-release" for the tags 18.41.39 # gevaerts: I agree, but I thought there was some reason I didn't understad for not doing that? 18.43.00 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 18.43.04 # AlexP: I thought that this was the latest thinking, sweeping away all possible earlier objections 18.43.24 # ok, I just briefly skimmed the log 18.43.59 # If there are no technical reasons then I'd prefer v3.8 branches and 3.8-release tags or something similar 18.46.10 # ah, I just read Torne's email 18.46.14 # Seems sensible 18.46.43 # TheLemonMan: did you keep disassembling the fuze+ ROM ? 18.49.55 # nop, i moved onto the bootloader quite immediately, ill care about the usb part later 18.50.16 # I'm reading the sb handling part 18.50.16 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 18.50.35 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 18.50.50 # that's really painful to read :) And seem rather inefficient 18.51.55 # as 99% of their code heh 18.52.51 # Torne: We also need to keep the identifier reasonably short, otherwise it won't be fully visible on targets with small displays 18.53.18 # Torne: can you move things between refs/heads and refs/oldheads later on without breaking things for other people? 18.53.25 # It will scroll iirc, but deciphering something that's not just words while it's scrolling by isn't easy 18.53.54 # TheLemonMan: I mean, it goes 1) read 16-byte 2) interpret 1) 2) ... at least for the header part 18.53.58 # we'll see for the rest :) 18.54.49 # On archos bitmap there are 18 chars per line (rockbox default font), on the Clips, M3, and the iriver and iaudio remotes there are 21 chars. Player has just 11... 18.56.30 # "v3.9pre-44-g337e922-official" would be too long to be really practical, on all of those... 18.56.55 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 18.57.11 # The "g337e922" is the most important part, so I think we can't really afford cutting that 18.57.52 # Our current scheme also includes the build date 18.58.16 # hm, right 18.59.01 # I'm not sure whether it's important with git - currently it is useful if you test something locally, as your base revision (from svn) won't change 19.01.00 # Current one uses 13 chars in total for an svn build including the 'M' 19.02.17 Join [Saint] [0] (~st.lasciv@119.224.72.2) 19.02.32 *** Saving seen data "./dancer.seen" 19.02.40 Quit bluebrother (Disconnected by services) 19.02.41 Quit [Saint] (Client Quit) 19.02.41 Join bluebroth3r [0] (~dom@rockbox/developer/bluebrother) 19.03.14 Quit TheLemonMan (Quit: Ex-Chat) 19.05.42 # B4gder/ Zagor: What's up with the build server? 19.06.07 # zagor isn't here, I have no idea 19.06.10 # what's wrong? 19.06.51 # The table shows it took 48 minutes for building 30108, almost all with empty logs 19.06.57 # 30109 wasn't built at all 19.07.30 # * amiconn also still misses the build system "kick" interface for committers 19.09.17 # Hmm, only 2 clients?? 19.09.30 # One did 8 builds, the other did none? 19.11.50 Join adisbladis [0] (~user@2001:67c:2a0:9:216:3eff:fe6b:13eb) 19.13.23 Quit jordan` (Quit: Coyote finally caught me) 19.14.26 # gevaerts: yes, you can move ref heads around 19.15.11 # Torne: ok, in that case I'd move non-current release branches to oldheads as well 19.15.50 # gevaerts: yeah, probably i guess. 19.16.30 Quit swilde (Remote host closed the connection) 19.16.54 Join fyrestorm [0] (~nnscript@cpe-24-90-84-81.nyc.res.rr.com) 19.17.33 # gevaerts: the way cloning works is you get everything under refs/heads, and you get everything under refs/tags *if* it refers to an object you actually downloaded 19.17.53 # it doesn't download more history just because a tag points to it 19.18.00 # (unless you tell it to) 19.18.07 # right 19.18.18 # you can write your own refspec in your local config, which can map anything to anything 19.18.22 # And refs isn't actually part of the hashed content then I guess 19.18.32 # No, refs are just.. symlinks, basically 19.18.48 # The actual tag objects are real objects 19.19.00 # (so that they can carry descriptions/signatures/etc) 19.19.14 # the ref for a tag just points at the tag object, which then in turn points to the commit 19.19.41 # amiconn: I'm not sure date is so important here - it is useful currently as it is difficult to know immediately when an svn revision was, but with e.g. 3.9pre44 it is much more obvious. 19.37.17 # The build date can wildly differ from the date a revision has been commited 19.38.04 # Forinstance when you're bisecting 19.38.33 # yes, but does that matter? 19.39.01 # I guess what I'm asking is, is the build date useful for anything other than knowing when a current buuld that someone was using was current? 19.55.57 Quit Horscht (Read error: Connection reset by peer) 19.56.06 Join Horscht [0] (~Horscht@xbmc/user/horscht) 19.59.32 Join mudd1 [0] (~cmertes@ip-78-94-202-227.unitymediagroup.de) 20.01.39 Quit asper (Quit: CGI:IRC) 20.07.09 Join Guinness` [0] (Slayer@c-68-55-111-159.hsd1.va.comcast.net) 20.09.02 Join stoffel [0] (~quassel@p57B4C15B.dip.t-dialin.net) 20.10.23 Quit Guinness (Ping timeout: 255 seconds) 20.10.36 Quit Guinness` (Read error: Connection reset by peer) 20.21.05 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 20.37.18 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 20.48.37 Join esperegu [0] (~quassel@145.116.15.244) 20.54.40 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 20.55.03 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 20.57.18 Join dan_a [0] (d917ad9c@gateway/web/freenode/ip.217.23.173.156) 20.58.11 Join thomasjfox [0] (~thomasjfo@rockbox/developer/thomasjfox) 21.02.35 *** Saving seen data "./dancer.seen" 21.02.58 Join [Saint] [0] (~st.lasciv@119.224.72.2) 21.18.22 Quit ReimuHakurei (Quit: If I use this, I will disappear, and Shana-tan will remain...) 21.19.47 Join ReimuHakurei [0] (~reimu@74.112.212.15) 21.23.14 Join Guinness [0] (Slayer@c-68-55-111-159.hsd1.va.comcast.net) 21.24.03 Quit MethoS- (Remote host closed the connection) 21.24.04 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 21.27.41 Join keyb_gr [0] (~chatzilla@p4FF02045.dip.t-dialin.net) 21.40.07 # omg, I'm a fucking genius 21.46.22 # pamaury: ...are you? 21.46.31 # yes definitely :) 21.46.33 # what did you invent? :) 21.46.49 # nothing 21.47.09 # I just discovered something useful out of the freescale ROM disassembly 21.47.38 # that undoubtly qualify as being a genius ;) 21.47.42 Join Strife89 [0] (~Strife89@207-144-19-39.cstel.net) 21.48.11 # and this also explains how the fuze+ boots, but that a minor point :D 21.50.46 # nice 21.51.53 # I did not understand how a boot section could pass control to another but the answer is simple: it gives a hidden argument to the entry point which is a pointer so that if you write the id of the next section, the ROM bootloader will branch to it 21.54.15 # genius! 21.54.22 # I told you... 21.54.31 # :) 21.54.59 Quit [Saint] (Quit: Imagination is for turbo-nerds who can't handle how kick-butt reality is. I'm a kick-butt reality master! I would rather die, than be imaginative. I mean that.) 21.55.24 # So actually, we will be be able to dual boot on the fuze+, the only *minor* point is that any OF update will destroy the bootloader... 21.56.37 Join [Saint] [0] (~st.lasciv@119.224.72.2) 21.56.40 # is that fixable? 21.57.10 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 21.57.10 # yes of course, by destroy I mean the rockbox bootloader will be gone, you will only be able to boot the OF and will need to reinstall it 21.57.51 # That's the case on a lot of players though, so I don't think that's really a big deal. 21.58.08 # Another problem is that if *by chance* the OF check the bootloader at each boot and overwrite it if it sees a difference, then you can't really call that dual-boot :) 21.58.49 # it would be a (rockbox-many/of-once)-boot 21.59.40 # That's the case on the Gigabeat F (or was for quite a while) where it wasn't dual boot so much as "restore the OF bootloader if you want to get in the OF" 22.00.00 # Another option is to use the i2c chip on the device but it's only 64kb large so fitting the bootloader in that would be a bit of pain I guess 22.01.47 # Llorean: I think it still is 22.01.55 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 22.01.56 # Couldn't swear to it though 22.03.31 # 64k is plenty 22.03.38 Quit Strife89 (Ping timeout: 240 seconds) 22.04.02 # kugelp: with hardware init that becomes a lot less quickly 22.04.41 # two stage loader perhaps? 22.05.53 # but where do you store the second one ? 22.06.02 # I would think that a bl fits into 64k without bitmaps but I may be wrong 22.06.56 # I need to check this 22.06.57 # pamaury: on disk? 22.07.43 # well but then you can load rockbox.directly 22.09.39 Quit stoffel (Remote host closed the connection) 22.09.46 # you still need to do the hardware init :) Nothing is impossible of course, but I just would like to make it as simple as possible 22.14.43 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 22.18.21 Quit [Saint] (Quit: Imagination is for turbo-nerds who can't handle how kick-butt reality is. I'm a kick-butt reality master! I would rather die, than be imaginative. I mean that.) 22.20.12 Join [Saint] [0] (~st.lasciv@119.224.72.2) 22.21.21 Join krazykit [0] (~krazykit@206.183.182.189) 22.33.59 Quit [Saint] (Quit: Imagination is for turbo-nerds who can't handle how kick-butt reality is. I'm a kick-butt reality master! I would rather die, than be imaginative. I mean that.) 22.35.28 Join [Saint] [0] (~st.lasciv@119.224.72.2) 22.38.06 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 22.38.26 Quit benedikt93 (Quit: Bye ;)) 22.41.39 Join einhirn [0] (~Miranda@p5485108B.dip0.t-ipconnect.de) 22.42.10 Quit einhirn (Client Quit) 22.43.33 # pamaury: I don't know how much hardware init you have to do, but many rockbox bootloaders which have to do hardware init are smaller than 64K 22.45.49 # as I said, the problem is not much about the "if" but about the "how". Fitting it into 64kb would probably mean to rewrite the low level init stage which I extract from the OF 22.45.56 # which include the sdram init 22.46.00 # and which is a pain 22.46.49 # that would probably save 20kb, plus the bitmap image and stripping useless thing you can probably fit this 22.47.26 Quit thomasjfox (Read error: Connection reset by peer) 22.50.22 Quit mc2739 (Ping timeout: 240 seconds) 22.52.27 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 22.55.47 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 22.55.59 # What bitmap? No rockbox bootloader contains a bitmap afaik (apart from the sysfont to be precise) 22.56.08 Join powell14ski_ [0] (~powell14s@c-174-51-194-6.hsd1.co.comcast.net) 22.56.19 # I believe some Sansas do 23.00.14 Quit tchan (Quit: WeeChat 0.3.5) 23.00.23 # yes it does 23.00.30 # but you can disable it 23.00.47 # amiconn: most do actually 23.01.05 # most? 23.02.38 *** Saving seen data "./dancer.seen" 23.03.26 # Archos bootbox doesn't, the iriver, iaudio, all ipod (<= 5.5G) bootloaders don't. c200v1 bootloader doesn't either 23.03.48 # all sansas, abs i thought ipods too? 23.04.50 # also i seem to remember the change was applied to all bootloaders? 23.04.58 # That's already 21 if I'm counting correctly 23.05.07 # some of probably were not released since then 23.07.02 # I'm quite confident that it's not wanted or even possible on all due to size constraints 23.09.40 Quit [Saint] (Quit: Imagination is for turbo-nerds who can't handle how kick-butt reality is. I'm a kick-butt reality master! I would rather die, than be imaginative. I mean that.) 23.11.20 Join [Saint] [0] (~st.lasciv@119.224.72.2) 23.12.47 # kugel: Have you taken note of jhMikeS' and my observation that the file browser shows trashed file names (one in each directory) when dircache is enabled? 23.13.15 # This is true even with Slasheri's latest commits 23.15.37 Quit [Saint] (Client Quit) 23.17.00 Join [Saint] [0] (~st.lasciv@119.224.72.2) 23.21.15 Quit [Saint] (Client Quit) 23.25.06 Join [Saint] [0] (~st.lasciv@119.224.72.2) 23.26.03 Quit esperegu (Read error: Connection reset by peer) 23.30.24 Join Stummi [0] (~Stummi@rockbox/developer/Stummi) 23.33.01 Quit [Saint] (Quit: Imagination is for turbo-nerds who can't handle how kick-butt reality is. I'm a kick-butt reality master! I would rather die, than be imaginative. I mean that.) 23.36.46 Join TheLemonMan [0] (~lem0n@ppp-219-30.26-151.libero.it) 23.45.27 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 23.57.41 Join tchan [0] (~tchan@lunar-linux/developer/tchan)