--- Log for 04.12.113 Server: holmes.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 4 days and 13 hours ago 00.04.59 Quit wodz (Quit: Leaving) 00.05.18 Quit Narod () 00.06.22 Quit kugel_ (Ping timeout: 245 seconds) 00.06.23 Join krabador [0] (~krabador_@unaffiliated/krabador) 00.10.07 # haha, I found the code of the production test mode :) 00.11.18 Quit ender` (Quit: I like work: it fascinates me. I can sit and look at it for hours. -- Jerome K. Jerome) 00.13.16 # my device definitely has a fm tuner, it's just a software limitation 00.16.35 # great 00.17.09 # It's probably due to the European tax on FM tuners 00.17.28 # some manufacturers disable it in Europe to sell the device cheaper or increase their margin 00.22.01 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 00.35.04 Join chrisjj [0] (561bb732@gateway/web/freenode/ip.86.27.183.50) 00.35.07 # Devs, May one assume all references to SVN for current procedures are obsolete? e.g. http://www.rockbox.org/wiki/FlySprayHowto "Please include: The SVN revision/release you are using and if possible the particular SVN revision in which you think the bug was introduced." 00.36.04 # chrisjj: yeah, now we use git commit id (usually short ids) 00.36.09 *** Saving seen data "./dancer.seen" 00.37.42 # So, is "git commit ID" the official terms for e.g. the pre-dash part of the Rockbox System, Info, Version: ? 00.38.48 # no, the git commit id only replaces the SVN revision 00.39.59 # ah ok, misunderstood the "pre-dash" 00.40.00 # OK, so what term would you use for the pre-dash part of the Rockbox System, Info, Version: e.g.9ff1819 ? 00.40.14 # yeah it's a abbreviate/short commit id 00.40.20 # OK! So answer is Yes? 00.40.28 # OK, got it. 00.40.38 # yes, I thought you were suggesting the commit replaced everything sorry 00.40.43 # I'm going to change "Please include: The SVN revision/release you are using and if possible the particular SVN revision in which you think the bug was introduced." to... 00.41.23 # "Please include: The version number of the Rockbox version you are using and if possible the version number of the Rockbox version in which you think the bug was introduced." 00.41.32 # OK? 00.43.24 # I find it a bit obscure 00.43.47 # OK, what's better? 00.45.05 # I would rather replace the whole sentence by: "Please include the Rockbox release and if possible the version displayed in the system information (git commit ID)" 00.45.18 # *release version number 00.46.47 # OK, but where does a user find the Rockbox release version number on the device? 00.48.30 # I'm not sure, I never run an official release. I think the system info displays the release if it's a release build and the git commit id otherwise 00.48.43 # So yeah, let's it be only "the version displayed in the system info" 00.48.54 # that's always the most precise information anyway 00.50.55 Quit nosa-j (Read error: Operation timed out) 00.53.46 # OK, so "Please include the Rockbox version indentifier, found at System>Info, e.g. 9ff1819-131202" 00.53.58 # Looks OK? 00.57.13 Join nosa-j [0] (~m00k@66.233.224.206) 00.58.53 # yeah perfect 01.03.31 # Thanks, done. 01.04.17 Quit nosa-j (Ping timeout: 245 seconds) 01.04.23 # Hey, what do you think about the idea of a version terminology cleanup week?? 01.04.55 # I guess there are *lots* of places on the wiki which still refer to the SVN 01.05.06 # Only kidding :) 01.05.25 # I'll amend any SNV version references I see... 01.06.26 Quit bertrik (Ping timeout: 248 seconds) 01.07.21 # I wanted to ask your thoughts on the ZEN BSoD. Putting aside the "black screen" part, what do you think might be causing the "death" i.e. the non-responsiveness to buttons? 01.07.54 # I won't say **the cpu crashed** again :) but clearly the CPU is stuck somehow. 01.10.09 # well, if I read correctly that the bootloader always manage to print something on the screen, and since the bootloader and rockbox code are running the same code, I think it might be due to some timing problem. For example some irqs or threads running in parallel of the lcd init and somehow disturbing it 01.10.12 # but that's just a guess 01.10.54 # the bootloader and rockbox don't have exactly the same init code 01.11.43 Join nosa-j [0] (~m00k@66.233.224.206) 01.13.11 Quit GodEater (Ping timeout: 246 seconds) 01.13.58 # Sure that could cause the black screen... but I'm thinking about what could cause the death. 01.14.07 # The death is a CPU state, not an LCD state. 01.14.49 # I wonder what actual state the CPU is in when "dead"... and how on earth any problem with the LCD code could get it there. 01.16.39 # my other theory is that it is related to power management 01.16.58 # that's the typical source of cpu hang with explaination 01.19.08 Quit nosa-j (Ping timeout: 246 seconds) 01.23.04 Quit lebellium (Quit: ChatZilla 0.9.90.1 [Firefox 26.0/20131125215016]) 01.23.45 # So that CPU hang is what, precisely? Infinite loop? 01.23.49 Join JdGordon1 [0] (~jonno@rockbox/developer/JdGordon) 01.24.38 # is that's a power problem, it's a hung state, probably voltage brownout or something 01.24.42 # *if 01.25.16 # or pure and simple cpu lock up, strange things can happen when you drive the cpu out of the safe lands :) 01.25.32 Quit JdGordon| (Ping timeout: 245 seconds) 01.26.08 # Oh, you mean the voltage on CPU Vcc is inadequate? 01.27.29 # the power management is complicated, if you don't do the right things in the right order, you can cause VDD or VDDIO brownouts yes 01.27.47 # I ran into many such problems on imx233 in the early development 01.28.12 # but again, just a theory 01.28.40 # however there should be a way to test it using the watchdog and reset maybe 01.29.13 # can you compile rockbox or not ? 01.30.33 # No I can't compile. 01.30.45 Join nosa-j [0] (~m00k@66.233.224.206) 01.31.45 Join Scr0mple [0] (~Simon@161.43.73.67) 01.31.58 # they still are a few things to try out, like commenting the whole power setup code, add watchdog handler to blink the power led on massive failure and so on 01.33.37 Quit Scromple (Read error: Connection reset by peer) 01.34.11 Quit Mir (Read error: Connection reset by peer) 01.34.31 Join GodEater [0] (~whoknows@cl-711.lon-02.gb.sixxs.net) 01.34.31 Quit GodEater (Changing host) 01.34.31 Join GodEater [0] (~whoknows@rockbox/staff/GodEater) 01.34.51 Join Mir [0] (~Mir@pool-71-109-219-225.lsanca.dsl-w.verizon.net) 01.39.32 Quit pamaury (Ping timeout: 245 seconds) 01.45.37 Join JdGordon| [0] (~jonno@ppp118-209-182-215.lns20.mel6.internode.on.net) 01.45.41 Quit JdGordon| (Changing host) 01.45.41 Join JdGordon| [0] (~jonno@rockbox/developer/JdGordon) 01.46.37 Join Chuckery [0] (474b6423@gateway/web/freenode/ip.71.75.100.35) 01.46.45 # hallo everybody 01.46.47 Quit JdGordon1 (Ping timeout: 246 seconds) 01.46.56 # hello 01.47.06 # how are you doing today? 01.49.23 # hello? 01.50.22 Join treaki_ [0] (c2e23fd39d@p4FDF7E5C.dip0.t-ipconnect.de) 01.51.26 # i'm great and yourself? 01.51.50 # pretty good 01.51.59 # rockbox seems pretty cool 01.52.19 # but what I'm really looking at is some sort of mod for the ipod nano 7th generation 01.52.29 # been shuffling through the files 01.52.32 # pain in the arse 01.52.35 Quit treaki__ (Ping timeout: 245 seconds) 01.54.39 # seems like the sort of software that rockbox uses 01.54.55 # need to be completely redone in order for it to allow use on the 7g platform 01.54.59 # thoughts? 01.55.00 # also 01.55.13 # I tried loading some modified firmware on the ipod 01.55.16 # and it flipped shit 01.55.22 # went black 01.55.28 # wouldn't mount 01.55.41 # finally if came back on after about 5 hours 01.55.52 # dunno what happened 01.55.56 # thoughts? 01.57.21 Quit zoktar (Quit: -) 01.58.08 # hello? 01.59.06 # hi 01.59.27 # hello 01.59.36 Quit nosa-j (Ping timeout: 252 seconds) 02.00.03 # no clue about Apple devices only know that I've read the firmware is encrypted or something like this 02.00.19 # there is work in progress to have rockbox as an app 02.00.32 # meanwhile you might try VideoLAN Client for iOS 02.02.57 # nah bruh 02.03.01 # this isn't ios 02.03.17 # this is the weird shit that apple put on the new ipod nano 02.03.19 # oh okaya 02.03.19 # 7th generation 02.03.59 # I have Sansa Fuze / Clip / and also Android devices so I won't know much about your Apple device sorry 02.04.12 # that's fine 02.04.22 # I was just wondering if anybody had ideas about it 02.04.33 # I think my issue with the bricking stuff 02.04.49 # is that it freaks out after realizing the cache is not correct 02.04.59 # I used to be able to bypass that with nanohack.me 02.05.04 # but the site has gone down since 02.05.08 # and I don't have the program 02.05.52 Join nosa-j [0] (~m00k@66.233.224.206) 02.07.42 # thoughts? 02.09.19 Quit dfkt (Read error: Connection reset by peer) 02.09.21 Join dfkt [0] (dfkt@unaffiliated/dfkt) 02.10.31 Quit nosa-j (Ping timeout: 240 seconds) 02.18.06 Join zoktar [0] (~zoktar@unaffiliated/zoktar) 02.22.55 Join amayer [0] (~amayer@h62.30.25.72.ip.windstream.net) 02.27.46 # is gerrit still down? i get 503 02.32.04 # I was kind of eager to see the new one 02.33.44 Quit Chuckery (Quit: Page closed) 02.36.12 *** Saving seen data "./dancer.seen" 02.37.30 Quit futurisk (Ping timeout: 272 seconds) 02.44.20 Join futurisk [0] (~futurisk@9mm.607hosting.us) 02.44.32 Quit futurisk (Read error: Connection reset by peer) 02.54.51 Join [Saint] [0] (~saint@rockbox/user/saint) 03.09.26 Quit krabador (Quit: Sto andando via) 03.26.12 Join JdGordon1 [0] (~jonno@rockbox/developer/JdGordon) 03.27.46 Quit JdGordon| (Ping timeout: 248 seconds) 03.37.23 Join Zambezi_ [0] (Zulu@bnc.fran.hostbay.nu) 03.37.45 Quit Zambezi (Read error: Connection reset by peer) 03.59.58 Join rewrite [0] (~rewrite@unaffiliated/rewrite) 04.03.32 Join endee [0] (sid15467@gateway/web/irccloud.com/x-bzadgczyxojinsei) 04.17.35 Quit amayer (Quit: Leaving) 04.21.41 Quit Scr0mple (Ping timeout: 248 seconds) 04.22.54 Quit Provel (Ping timeout: 246 seconds) 04.23.12 Join Provel [0] (~Provel@75-132-18-44.dhcp.stls.mo.charter.com) 04.30.45 Quit Provel (Ping timeout: 248 seconds) 04.31.47 Join Provel [0] (~Provel@75-132-18-44.dhcp.stls.mo.charter.com) 04.36.14 *** Saving seen data "./dancer.seen" 04.36.15 Quit Provel (Ping timeout: 245 seconds) 04.37.04 Join Provel [0] (~Provel@75-132-18-44.dhcp.stls.mo.charter.com) 04.44.17 Quit Provel (Ping timeout: 252 seconds) 04.47.12 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 04.47.12 Quit pixelma (Disconnected by services) 04.47.13 Quit amiconn (Disconnected by services) 04.47.13 Join amiconn_ [0] (amiconn@rockbox/developer/amiconn) 04.47.13 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma) 04.47.15 Nick amiconn_ is now known as amiconn (amiconn@rockbox/developer/amiconn) 05.03.26 Join Provel [0] (~Provel@75-132-21-67.dhcp.stls.mo.charter.com) 05.10.25 Quit [Saint] (Remote host closed the connection) 05.11.42 Join krabador [0] (~krabador_@unaffiliated/krabador) 05.12.13 Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs) 05.12.29 Quit Provel (Ping timeout: 245 seconds) 05.12.34 Join [Saint] [0] (~saint@rockbox/user/saint) 05.15.51 Join Provel [0] (~Provel@75-132-21-67.dhcp.stls.mo.charter.com) 05.17.40 Quit zoktar (Ping timeout: 245 seconds) 05.42.07 # <[Saint]> Gah. 05.46.10 # <[Saint]> That's slightly annoying. Warble freaks out if you clean the build folder. 05.46.59 # <[Saint]> and you apparently can't pick it up and move it around without annoying it either. 05.53.19 Quit TheSeven (Disconnected by services) 05.53.32 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 06.17.56 Join cmhobbs_ [0] (~cmhobbs@ip70-178-52-92.ks.ks.cox.net) 06.19.12 Quit krabador (Quit: Sto andando via) 06.20.05 Quit michaelni (Read error: Connection timed out) 06.22.20 Quit cmhobbs (Ping timeout: 245 seconds) 06.22.23 Quit Bluefoxicy (Ping timeout: 245 seconds) 06.22.27 Quit Provel (Ping timeout: 245 seconds) 06.22.34 Join Bluefoxicy [0] (~Bluefoxic@c-76-21-157-203.hsd1.md.comcast.net) 06.22.44 Join Provel [0] (~Provel@75-132-21-67.dhcp.stls.mo.charter.com) 06.23.26 Join michaelni [0] (~michael@chello084114129144.4.15.vie.surfer.at) 06.30.07 Join mortalis [0] (~kvirc@213.33.220.118) 06.34.32 Quit cmhobbs_ (Ping timeout: 246 seconds) 06.36.16 *** Saving seen data "./dancer.seen" 06.41.29 Join Scromple [0] (~Simon@161.43.73.67) 06.47.11 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee) 07.01.53 Join dfkt_ [0] (dfkt@unaffiliated/dfkt) 07.03.23 Quit dfkt (Ping timeout: 240 seconds) 07.30.12 Join [Saint_] [0] (~saint@rockbox/user/saint) 07.31.11 Quit [Saint] (Ping timeout: 246 seconds) 07.58.34 Quit Provel (Read error: Connection reset by peer) 07.59.45 Nick [Saint_] is now known as [Saint] (~saint@rockbox/user/saint) 08.02.41 Join Provel [0] (Provel@75-132-21-67.dhcp.stls.mo.charter.com) 08.19.56 Join ender` [0] (krneki@foo.eternallybored.org) 08.22.11 Join zoktar [0] (~zoktar@unaffiliated/zoktar) 08.36.19 *** Saving seen data "./dancer.seen" 08.51.47 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 08.57.40 Quit kevku (Ping timeout: 245 seconds) 09.02.25 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 09.11.34 Join fragilematter [0] (~fragilema@unaffiliated/fragilematter) 09.17.13 Quit maraz (Ping timeout: 245 seconds) 09.17.20 Join maraz [0] (maraz@kapsi.fi) 09.18.30 Join petur [0] (5bb7304d@rockbox/developer/petur) 09.20.33 Quit vedos (Ping timeout: 245 seconds) 09.20.40 Join draft [0] (draft@disharmony.fi) 09.29.57 Quit bertrik (Ping timeout: 248 seconds) 09.34.55 # Zagor: what happened with gerrit? 09.37.44 Join maruk [0] (~papier@titanium.v6.sdv.fr) 09.39.34 # Upgrade gone wrong I'm guessing :) 09.40.19 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 09.42.34 Quit scorche (Read error: Connection reset by peer) 09.43.13 Join scorche [0] (~scorche@rockbox/administrator/scorche) 09.47.21 Join JdGordon| [0] (~jonno@ppp118-209-228-64.lns20.mel6.internode.on.net) 09.47.21 Quit JdGordon| (Changing host) 09.47.21 Join JdGordon| [0] (~jonno@rockbox/developer/JdGordon) 09.47.31 Join kevku [0] (~kevku@2a01:d0:ffff:34a::8:3) 09.48.55 Quit JdGordon1 (Ping timeout: 245 seconds) 09.56.52 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 10.03.02 Quit solrize__ (Ping timeout: 240 seconds) 10.04.33 Join endee_ [0] (sid15467@gateway/web/irccloud.com/x-btonklyezyetkjjr) 10.11.21 Join Poodlemastah_ [0] (~Poodlemas@109-124-181-96.customer.t3.se) 10.12.16 Quit endee (*.net *.split) 10.12.17 Quit rewrite (*.net *.split) 10.12.17 Quit Poodlemastah (*.net *.split) 10.12.17 Quit froggyman (*.net *.split) 10.12.20 Nick endee_ is now known as endee (sid15467@gateway/web/irccloud.com/x-btonklyezyetkjjr) 10.26.49 Join JdGordon1 [0] (~jonno@rockbox/developer/JdGordon) 10.27.35 Quit JdGordon| (Ping timeout: 246 seconds) 10.36.20 *** Saving seen data "./dancer.seen" 10.49.57 Nick SuperBrainAK is now known as DormantBrain (~andy@2001:470:8:a61::5f92:59a1) 11.07.07 # hum, I didn't touch gerrit 11.11.19 # restarted 11.17.27 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 11.19.50 Join froggyman [0] (~frogs@173.234.239.23) 11.19.50 Join rewrite [0] (~rewrite@2604:180::71a9:fbc3) 11.20.18 Quit froggyman (Changing host) 11.20.18 Join froggyman [0] (~frogs@unaffiliated/froggyman) 11.20.18 Quit rewrite (Changing host) 11.20.18 Join rewrite [0] (~rewrite@unaffiliated/rewrite) 11.20.28 # wodz: thanks for the info on the SDRAM ! How did you find out ? I couldn't find a datasheet 11.20.39 # 2MB is not a lot, I thought it would have more :-/ 11.29.14 # pamaury: my google-fu is strong today! 11.30.15 # hey that's unfair, today I typed the *exact* same search string as yesterday and now the datasheet is the second result 11.30.54 # and incidentally, I had the datasheet on my hard drive but only realised it this morning 11.31.02 # pamaury: different computer? google returns different results for me on home machine and when I am at work 11.31.37 # I guess it tracks your queries history or something 11.39.45 # pamaury: Did you try current version of clang to build rb for arm? 11.40.10 # nope, maybe I can try again tonight, but I'm lazy, building clang takes hours 11.40.33 # I think they are in RC, maybe they have a prebuilt version 11.40.47 # no, they don't 11.41.44 # ok, I'll launch a compile now then, to be sure it's working tonight ^^ 11.42.11 # also it takes Gigas of disk space 11.42.26 # Or at least I couldn't find it. It took about 2h to compile on my box. Compilation is considerably faster with -j1 as single thread takes 2-3GB of mem so with more threads it starts to swap on my box 11.43.42 # I already had to download and recompile kate myself two days ago, I'm trying to track a memory leak and I already help found one bug 11.44.10 # whats kate? 11.44.50 # text editor 11.45.28 # I hope you are not a dangerous user of Vim or Emacs, are you ? 11.45.51 # * wodz is proud user of Vim ! 11.46.14 # kate has a Vi mode :p but no one seriously use that I think 12.36.21 *** Saving seen data "./dancer.seen" 12.52.55 Quit [Saint] (Quit: Quit.) 12.55.38 Join [Saint] [0] (~saint@rockbox/user/saint) 12.59.25 # Possible idea: menu for sound setting profiles, example to change between loudspeaker and headphone profile, changing config file even from shortcuts add one unnessesery step and is not clean solution to day to day use 13.00.19 # Or shortcut to config file could load file straight from one select press, not show user the .rockbox folder with all files 13.03.52 # Ketturi: I'm not sure I understand, is that so hard to go into Settings > Load/Restore/Save ? Or just change one setting when you need ? 13.06.13 # well not that hard, but doing that settings -> load path every time changing between headphones and speakers is bit anoying, but still best solution it seems 13.07.32 # which target ? 13.09.39 # ipod, which i must admit is very intuitive to move in menus, better than some other devices 13.10.21 Join lebellium [0] (~chatzilla@80.215.32.80) 13.12.49 Quit petur (Quit: Page closed) 13.15.10 # I was not aware that we supported the speaker on some ipods 13.16.07 # which one? 13.17.19 # or I misunderstood which setting(s) you are referring to 13.18.22 # maybe he's referring to external active speakers 13.18.54 Quit JdGordon1 (Ping timeout: 240 seconds) 13.19.25 # yah, external speakers, which could not be detected as they use normal audio out 13.20.23 # ah ok, so you have different set of audio parameters for different situations 13.20.54 # so your problem is that load/save saves all settings and you would prefer to only touch the audio ones 13.21.10 Join JdGordon| [0] (~jonno@ppp118-209-88-107.lns20.mel4.internode.on.net) 13.21.10 Quit JdGordon| (Changing host) 13.21.10 Join JdGordon| [0] (~jonno@rockbox/developer/JdGordon) 13.43.09 # * [Saint] can't see why Shortcuts isn't an adequate solution. 13.54.11 # Anyone here have the FiiO X3? 13.54.52 # No, those people are on head-fi :) 13.55.35 # haha yeah I guess so :/ 13.55.57 # Ketturi: also you can prepare config files that just include the settings you want to change 13.57.14 # <[Saint]> ah, yes, indeed. That's worth mentioning. my response kinda assumed that knowledge was present. 13.57.35 # pixelma: yeah I found that out, but still menu with settable profiles would be nice ;P 13.57.50 Join lebellium_ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 13.58.32 # <[Saint]> The problem is its /such/ a niche case, and the functionality is already there by way of the Shortcuts menu. 13.58.54 # <[Saint]> So, I wouldn't hold my breath, as it were. 13.59.00 Quit wodz (Read error: No route to host) 14.01.35 Quit lebellium (Ping timeout: 260 seconds) 14.01.44 Nick lebellium_ is now known as lebellium (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 14.02.04 # [Saint]: I would need to read up on the shortcuts menu actually but maybe you can give a quick answer... What can you put there if you want to change more than one setting at once (e.g. bass, treble and volume) - can you put config files there or something similar? 14.02.53 # You can but config files there, but shortcut leads to folder where they are 14.02.59 # so its like 3 clics or so 14.03.27 # <[Saint]> It'll definitely be at least that from a menu setting...so. 14.03.56 # <[Saint]> This wouldn't ever make it to the "main page" of the menu. 14.04.06 # <[Saint]> To be honest I doubt it would make it in at all. 14.05.07 # thout with ipods and audi out docs it could be made to automatically detect, when device is conneted 14.07.39 # <[Saint]> And what if you use several docks? Hope they all use the same audio configuration? 14.07.49 # so you would have a shortcut to lead you to the "Browse .cfg Files" in "Settings > Manage Settings"? Not sure that's worth it but maybe 14.08.22 # <[Saint]> pixelma: no, you have the shortcut lead you to whereever you left the file, with it selected as the current item. 14.09.01 # <[Saint]> basically, the caveat is having to press select twice. that's it. 14.29.27 Quit markun (Quit: leaving) 14.31.10 Join markun [0] (~markun@rockbox/developer/markun) 14.36.24 *** Saving seen data "./dancer.seen" 14.46.23 Join amayer [0] (~amayer@mail.weberadvertising.com) 14.46.54 Join cmhobbs_ [0] (~cmhobbs@ip70-178-52-92.ks.ks.cox.net) 15.01.25 Quit cmhobbs_ (Ping timeout: 264 seconds) 15.28.06 Join JdGordon1 [0] (~jonno@rockbox/developer/JdGordon) 15.29.38 Quit JdGordon| (Ping timeout: 246 seconds) 15.30.15 Quit kevku (Ping timeout: 260 seconds) 15.50.17 Join solrize [0] (solrize@unaffiliated/solrize) 15.50.22 Quit krnlyng (Ping timeout: 260 seconds) 16.16.57 Quit chrisjj (K-Lined) 16.16.58 Quit JdGord|w (K-Lined) 16.19.25 Quit Cultist (Ping timeout: 240 seconds) 16.21.52 Join Cultist [0] (~CultOfThe@c-24-12-53-28.hsd1.il.comcast.net) 16.36.26 *** Saving seen data "./dancer.seen" 16.39.46 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee) 16.42.31 Join krnlyng [0] (~liar@83.175.90.24) 16.51.09 Quit Cultist (Ping timeout: 250 seconds) 16.52.00 Join |akaWolf| [0] (~akaWolf@188.134.9.161) 16.52.25 Join Cultist [0] (~CultOfThe@c-24-12-53-28.hsd1.il.comcast.net) 16.54.34 Quit pamaury (Ping timeout: 245 seconds) 16.57.26 Join Narod [0] (Narod@p5DDDAE50.dip0.t-ipconnect.de) 17.01.58 Part fragilematter 17.11.40 Join eyfour [0] (~eyfour@84.202.76.176) 17.14.16 Join ikeboy [0] (~ikeboy@ool-435622d3.dyn.optonline.net) 17.16.36 Quit Cultist (Ping timeout: 272 seconds) 17.22.36 Join chrisjj [0] (561bb732@gateway/web/freenode/ip.86.27.183.50) 17.24.03 Quit amayer (Quit: Leaving) 17.25.28 Join Cultist [0] (~CultOfThe@c-24-12-53-28.hsd1.il.comcast.net) 17.26.25 Join amayer [0] (~amayer@mail.weberadvertising.com) 17.36.34 Join n1s [0] (~n1s@rockbox/developer/n1s) 17.51.15 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 17.56.19 Quit mortalis (Ping timeout: 246 seconds) 18.00.21 Quit ikeboy (Quit: ikeboy) 18.21.32 Join pretty_function [0] (~sigBART@123.252.213.170) 18.28.56 Join krabador [0] (~krabador_@unaffiliated/krabador) 18.31.52 Join JdGordon| [0] (~jonno@rockbox/developer/JdGordon) 18.33.14 Quit JdGordon1 (Ping timeout: 272 seconds) 18.35.29 Quit maruk (Quit: Leaving.) 18.36.29 *** Saving seen data "./dancer.seen" 18.54.48 Join bertrik [0] (~quassel@ip117-49-211-87.adsl2.static.versatel.nl) 18.54.48 Quit bertrik (Changing host) 18.54.48 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 19.03.12 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 19.07.10 Quit chrisjj (Ping timeout: 250 seconds) 19.11.39 Join mortalis [0] (~kvirc@213.33.220.118) 19.13.59 Join chrisjj [0] (561bb732@gateway/web/freenode/ip.86.27.183.50) 19.14.22 # Test 19.16.10 # chrisjj: yes ? 19.16.43 # Just checking... :) 19.18.35 # But since you are here, tell me please, from where precisely in the source tree comes the full device name ? e.g. the string "Creative Zen" in the heading here: http://www.rockbox.org/dl.cgi?bin=creativezen 19.19.04 Quit |akaWolf| (Quit: my exit) 19.20.42 # I think they come from here: http://git.rockbox.org/?p=www.git;a=blob;f=buildserver/builds;h=dbfcca1e47bc0978d3d50ccb9f638e03654ae280;hb=HEAD 19.26.28 # Thanks but then how come the two show different casing "Creative Zen" v "Creative ZEN" ? 19.27.32 Quit krabador (Quit: Sto andando via) 19.28.32 Join krabador [0] (~krabador_@unaffiliated/krabador) 19.30.43 # must come from something else then ^^ 19.31.41 # could be this: http://git.rockbox.org/?p=rockbox.git;a=blob;f=tools/builds.pm;h=43e5291f1fcfde376e7119c97abf587944d4f32d;hb=HEAD 19.31.50 # I don't know how exactly this page is generated 19.31.59 Quit eyfour (Quit: WeeChat 0.3.7) 19.33.10 Quit chrisjj (Ping timeout: 250 seconds) 19.34.20 Join chrisjj [0] (561bb732@gateway/web/freenode/ip.86.27.183.50) 19.37.58 Join chrisjj_ [0] (561bb732@gateway/web/freenode/ip.86.27.183.50) 19.38.31 # I'd hope that is generated from tools\configure http://git.rockbox.org/?p=rockbox.git;a=blob;f=tools/configure;h=b33c798a3a783e17ff86e4bc80372806203e762c;hb=HEAD 19.38.48 Quit chrisjj (Ping timeout: 250 seconds) 19.39.43 Join chrisjj [0] (561bb732@gateway/web/freenode/ip.86.27.183.50) 19.40.12 # chrisjj_: no, configure is just a technical tools to do the build 19.40.33 # tools/builds.pm tells the status of the ports and what should be build on release (more or less) 19.40.37 # "technical tools"? Could you explain? 19.40.50 # you run it to compile rockbox 19.41.05 # So, what carries the info on a new port from tools/configure to tools/builds? 19.41.29 # it contains all the information to *compile* Rockbox, but it doesn't contain any information about the status target or whether we should release or whether the build server should build it 19.41.59 # first you edit configure, when target works you add it to tools/builds to have the build bots compile it on each commit 19.42.12 # err sorry to buildserver/builds 19.42.36 # and finally you add it to tools/builds.pm to give the target status, that's what is used by the website I think 19.42.42 Quit chrisjj_ (Ping timeout: 250 seconds) 19.43.34 # OK, thanks - I'll add a placeholder for that additional extra step to http://www.rockbox.org/wiki/PortingHowTo#tools_47configure 19.44.27 # well that's not really part of the porting procedure 19.44.47 # that's more about releasing than porting 19.46.39 # OK, then I'll wait for http://www.rockbox.org/wiki/ReleasingHowTo :) 19.47.35 # yeah we should definitely write this down 19.48.05 # Well, there is http://www.rockbox.org/wiki/ReleaseChecklist 19.48.10 # Not entirely up to date though 19.48.46 Join chrisjj_ [0] (561bb732@gateway/web/freenode/ip.86.27.183.50) 19.49.11 # it tells how to do the release but not how to add a player to the release or change its status 19.49.21 # We need Google Summer of Documentation :) 19.50.24 # if everyone who knew something important would write it down, that would already be a lot 19.50.45 # Excuse all the nick changes - freenode webclient has been crashing all day.() 19.50.49 # like me trying to documentation the porting procedure ^^ I've stalled we could say ;) 19.50.56 Quit chrisjj (Ping timeout: 250 seconds) 19.51.28 # These things have to be a two-man job IME. One thinks and talks, the other listens and writes. 19.54.13 # Back to the target name, it seems the ultimate source is target/configure ... except that some steps from that are manual and a little error-prone. 19.55.23 # Depends what you mean by target name: name displayed in Rockbox ? name displayed on the website ? name by the tools ? name in the manual ? We have multiple copies 19.55.38 Quit pretty_function (Remote host closed the connection) 19.56.19 # Well yes we do have multiple copies, and they are often inconsistent e,g, case Createive ZEN, Creative Zen. 19.56.57 # Tell me if I am wrong, but we'd hope for consistent name on RB, site, and manual, for sure. 19.57.24 # And we'd hope for correct name e.g. Creative ZEN, not Creative Zen. 19.58.26 # Personally I don't care but yeah I guess we'd hope for consistency, although ZEN vs Zen does not seem to be the biggest issue at the moment :) 19.58.44 # Perhaps I should say not "correct" but "official". 19.59.48 # Usually there is no single official name 19.59.48 # Well even RB is not the biggest issue at the moment :) 19.59.55 # Try e.g. finding how to capitalise iriver 20.01.23 # Um, no capitalisation, surely? 20.01.40 # It changes over time 20.03.10 # I think we need to concentrate on the internal names (like "sansafuzeplus"). Inconsistency there can cause actual issues. I dpnm 20.03.42 # I don't care much about the fancy other name 20.05.53 # A goos way to get consitent internal name would be to start with a consistent external name, and a simple policy rule to apply to it. 20.07.15 # So what do you do with things that have multiple external names? 20.07.20 # Currently the source seems to have three internal names - modelname target and t_model - and no external. 20.07.36 # The source doesn't need any external name 20.07.51 # chrisjj_: I think you must realise that what happen in real life in the opposite: people hack something and one day it works on sansafuzeplus, so they call it "Sansa Fuze+" 20.07.53 # ... and all three seems inconsistent... unless there's a policy here that I don't know. 20.08.45 # Sure I realise devs hack it. Just like I see users hack the RB binary... and get called stupid :) 20.09.46 # People are forced to hack where there's nothing better, e.g. something to tell them how to do it properly. 20.10.37 # Are there people hacking RB binary ? 20.11.17 # Multiple external names are not a problem. RB needs only one. I suggest the porter's job includes choosing the best... and writing it in to target//configure "official_name" or somesuch. 20.11.41 # They are 20.12.00 # P, yes e.g. http://forums.rockbox.org/index.php?topic=43507.0 20.12.28 # oh my... 20.12.29 # You're overlooking things that use the same firmware but are seen as different devices 20.13.42 # like the creativezen target which is actually compiled to Creative ZEN, ZEN X-Fi, ZEN V and ZEN Mozaic 20.17.14 # anyway, I understand we are not doing things perfectly but I think we achieve something reasonable with how current way of working 20.17.38 # *with our 20.18.00 # No, I'm not overlooking that. creativezen is not "the same firmware" for the different devices. 20.19.00 # And note that Creative ZEN, ZEN X-Fi, ZEN V and ZEN Mozaic *are* individual targets in /configure 20.19.07 # iaudio X5 X5L X5V 20.19.11 # but not in the source code 20.19.25 # Philips GoGear HDD1630 HDD1830 20.19.35 # Ipod 1G and 2G 20.19.37 # NWZ E380 / E370 20.19.43 # P, I agree the result is reasonable. All of RB is more than reasonable. But still we seek to improve, no? 20.20.54 # What do you think about putting the RB official device name in /configure? Then the code, site and manual can all take it from there, saving repeated manual copy and adjust. 20.21.58 # No 20.22.07 # it's not as simple, things get compiled/used in very different ways, it's actually more trouble than anything 20.22.08 # e.g. target_id=90 targetname="Creative ZEN" 20.22.12 # First of all, if it should be anywhere, it should be in builds.pm 20.22.22 # or similar 20.22.34 # configure is just one of the many users of the name 20.22.50 # In builds.pm even though the other three names are in configure? 20.23.29 # And in builds.pm even though the target is not there before release? 20.26.07 # If it's just a matter of a spelling, running grep on the entire source tree to check it the same everywhere seems no big deal 20.26.27 # far simpler than having complicated mechanism to write it in one place 20.33.58 # Wouold that be safe? I'd assumed there was some reason for the current three different spellings in configure. Else why would the second and third have been added? 20.34.21 # which spelling ? 20.35.08 # Spelling in e.g. http://pastebin.com/H4CZRvn1 20.35.26 # modelname="creativezen" target="CREATIVE_ZEN" t_model="creative-zen" 20.36.33 *** Saving seen data "./dancer.seen" 20.36.41 # these are *very* different: 20.36.41 # - modelname is the switch used to where running configure again (so it's local to configure) 20.36.41 # - target is the name of the #define used in the source to identify the target 20.36.41 DBUG Enqueued KICK pamaury 20.36.41 # - t_model is the name of the subdirectory under firmware/target/ 20.41.20 # No surprise there. :) 20.42.19 # notice none of them is displayed somewhere, these are all internal 20.42.43 Quit krabador (Read error: Connection reset by peer) 20.43.03 # actually modelname is not very local to the script since it's used by all the tools which call configure, so that's many of them ^^ That the most important one in fact 20.43.05 # So it seems to me ti would be very tricky to use a tree grep to check that all the spellings that should be the same are the same. 20.43.31 # you don't get it, these are ***internal***, they don't mean anything, they are not displayed 20.43.38 # I get it. 20.44.04 # your target could be called fuckingmanufacturer-stupiddac and display "Beautiful device on screen" ^^ 20.44.40 # Yup :) But where in the source would I define "Beautiful device on screen"?? 20.45.02 # To be clear: where would I define the variable having the value "Beautiful device on screen"? 20.45.19 # in the target config file, there is a #define which gives the name of the device to be displayed on the screen 20.46.07 # #define MODEL_NAME "Creative Zen" 20.46.55 # but I'm not sure it's even used somewhere 20.47.08 # maybe in some bootloaders and plugins 20.47.37 # be back soon 20.50.47 Join krabador [0] (~krabador@host36-176-dynamic.13-79-r.retail.telecomitalia.it) 20.50.49 Quit krabador (Changing host) 20.50.49 Join krabador [0] (~krabador@unaffiliated/krabador) 20.51.51 Quit pamaury (Ping timeout: 246 seconds) 20.52.21 Quit krabador (Client Quit) 20.56.55 Join kugel [0] (~kugel@91-66-52-103-dynip.superkabel.de) 20.56.55 Quit kugel (Changing host) 20.56.55 Join kugel [0] (~kugel@rockbox/developer/kugel) 20.59.07 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 20.59.22 Join krabador [0] (~krabador_@unaffiliated/krabador) 21.03.05 Nick Karrde- is now known as Karrde (alucard@karrde.kiserai.net) 21.18.38 Quit DuperMan (Remote host closed the connection) 21.25.03 Join rela [0] (~x@pdpc/supporter/active/rela) 21.38.08 Join Wardo [0] (~Mirandaha@176-120-190-109.dsl.ovh.fr) 21.48.16 Join lorenzo92 [0] (~chatzilla@2a02:27e8:10:746:0:dacc:0:1) 21.53.01 Quit pamaury (Ping timeout: 240 seconds) 22.05.13 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 22.06.09 Quit Provel (Ping timeout: 240 seconds) 22.09.08 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 22.11.03 Quit fs-bluebot (Ping timeout: 245 seconds) 22.12.04 Quit bluebrother^ (Ping timeout: 248 seconds) 22.12.24 Join fs-bluebot [0] (~fs-bluebo@f053155051.adsl.alicedsl.de) 22.20.32 Quit rela (Read error: Connection reset by peer) 22.25.21 Join wodz [0] (~wodz@87-207-223-0.dynamic.chello.pl) 22.25.26 # pamaury: ping 22.28.13 # wodz: pong 22.30.14 # pamaury: are blocking transfers used at all in rockbox usb? I spotted in rk27xx driver that struct endpoint_t defines semaphore for blocking transfers which is NOT volatile but it is released in IRQ context. I don't know if that matters but it is definitely a bug 22.30.46 # yeah blocking transfers are used 22.31.31 # ah indeed 22.32.17 # wodz: but isn't semaphore already volatile ? 22.32.50 # pamaury: BTW. after more detailed study of the driver for cusb2 in ralink sources I think I know all important bits to implement udc driver. 22.32.54 # pamaury: don't know 22.34.17 # kernel.h shows it has a few volatile fields 22.35.31 # yes 22.35.36 # yeah I think it's okay, the semaphore code is already irq protected and the fields which matter are volatile 22.36.14 # :-/ 22.36.35 *** Saving seen data "./dancer.seen" 22.37.00 # but you can try to see if it makes a difference :) 22.37.25 # this driver works on my dap/computer so I will not see any difference 22.40.29 Quit wodz (Quit: Leaving) 22.50.44 Join Provel [0] (Provel@75-132-21-67.dhcp.stls.mo.charter.com) 22.52.11 Nick DormantBrain is now known as SuperBrainAK (~andy@2001:470:8:a61::5f92:59a1) 22.55.58 Quit kevku (Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/) 22.56.51 Quit lebellium (Quit: ChatZilla 0.9.90.1 [Firefox 26.0/20131125215016]) 23.03.12 # gevaerts: in sd.h 23.03.13 # bool sd_removable(IF_MV_NONVOID(int drive)); 23.03.13 # bool sd_present(IF_MV_NONVOID(int drive)); 23.03.28 # that seems wrong, it should be IF_MD_NONVOID right ? 23.03.29 # Hmmm 23.03.30 # Yes 23.07.00 # yeah definitely, others storage systems use IF_MD 23.26.46 Quit kugel (Ping timeout: 260 seconds) 23.38.53 Quit lorenzo92 (Remote host closed the connection) 23.48.49 Quit n1s (Quit: Ex-Chat) 23.49.14 # yeah I managed to make i2c read work in PIO mode 23.49.17 Quit dfkt_ (Remote host closed the connection) 23.49.20 # even though the datasheet says it's impossible 23.50.56 # <[Saint]> s/impossible/...we tried and gave up/ 23.50.59 # <[Saint]> :) 23.51.16 # <[Saint]> (possibly didn't even try :)) 23.56.36 Join dfkt [0] (dfkt@unaffiliated/dfkt)