--- Log for 20.06.110 Server: hubbard.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 4 days and 5 hours ago 00.00.11 # bluebrother: this wish had been expressed a few times, also at DevCon IIRC :) 00.03.37 # pamaury: "/* idem but for i=0 */" idem is a french word 00.03.48 Quit M3DLG (Quit: RAGE QUIT) 00.04.08 # no it's a latin one 00.05.03 # But yeah I got the idea, I'll change that 00.06.38 *** Saving seen data "./dancer.seen" 00.09.07 # i saw some old posts suggesting that volume was a little low on amsv1 targets too compared to the OF 00.09.11 # has anyone else noticed this? 00.12.20 # saratoga, I find it hard to tell/compare, but I hardly ever go louder than -20 dB on my clipv1 00.13.17 # in other words, not anywhere near too low for me 00.13.25 Join AsusFreak [0] (www-data@giant.haxx.se) 00.14.09 # Another problem, and it was working last night, its telling me arm-elf-eabi-gcc command not found.... 00.14.37 # that means you either didn't build the compiler, or did not add it to your path 00.14.57 # it was working last night.........stupid cygwin...... 00.15.07 # AzureSky: launch rockboxdev.sh 00.15.08 # i'm guessing you exported it to the path? 00.15.13 # and build eabi 00.15.35 # and then closed cygwin 00.19.14 Part Jerom 00.20.18 Join Jerom [0] (~Jerom@79.132.53.242) 00.21.54 # Hi JdGordon, you remember me - the guy who tried to implement a pictureflow integration with the Cowon D2. You made it possible to use the toucharea "hotkey" tag for the D2. It worked like a charm for both 3x3 grid mode and absolute point mode. But now something seems to be broken. 3x3 grid mode works like a charme, absolute point mode does not at all. Clicking on my album art (which is defined as "hotkey" area will lead to nothing. May you check the cod 00.22.28 # To test this you may use the actual simulator with my AF_Flow theme.. 00.45.40 # And now with further testing: the ffwd tag seems to fail as well in absolute point mode. Hmmm. Can anybody check this please? 00.46.26 Join Gabe_G23 [0] (~gabe@bzflag/player/GabrielG) 00.47.16 Nick CGL is now known as CGL_emo (~CGL@190.207.202.226) 00.51.44 Nick bimbel is now known as bmbl (~Miranda@unaffiliated/bmbl) 00.52.43 Quit bertrik (Quit: De groeten) 00.57.59 Quit bmbl (Quit: Bye!) 01.09.10 Quit Jerom (Remote host closed the connection) 01.12.51 Quit whydoubt (Ping timeout: 265 seconds) 01.12.55 Join whydoubt [0] (~whydoubt@ip68-12-76-9.ok.ok.cox.net) 01.13.36 Quit bluebrother (Disconnected by services) 01.13.40 Join bluebroth3r [0] (~dom@rockbox/developer/bluebrother) 01.18.23 Quit ender` (Quit: Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. -- Seneca) 01.23.17 Quit DataGhost (Ping timeout: 276 seconds) 01.29.51 Quit AsusFreak (Quit: CGI:IRC (EOF)) 01.35.12 # the flash memory in my clip+ strikes me as pretty slow compared to other sansas, even in the OF 01.46.00 # maximizing profit by using cheaper parts, nothing surprising there really 02.06.39 *** Saving seen data "./dancer.seen" 02.12.26 Quit GeekShadow (Quit: The cake is a lie !) 02.13.57 Join BHSPitMini [0] (~BHSPitMon@tx-76-6-68-177.dhcp.embarqhsd.net) 02.22.24 Quit pamaury (Remote host closed the connection) 02.42.05 # saratoga, formatted it with the official SD formatting tool? 02.44.35 Join Strife1989 [0] (~Strife89@adsl-67-57-76.mcn.bellsouth.net) 02.47.51 Quit Strife89 (Ping timeout: 248 seconds) 02.52.18 # i was told to use the internal formatter rather then the sdformat tool, but i have done both on my players 02.54.17 # well its confirmed, 26937 is what broke microsd support for v2 fuze http://forums.rockbox.org/index.php?topic=25104.0 03.08.14 Quit BHSPitMini (Ping timeout: 264 seconds) 03.31.34 Quit krazykit (Ping timeout: 265 seconds) 03.34.49 Nick Strife1989 is now known as Strife89 (~Strife89@adsl-67-57-76.mcn.bellsouth.net) 03.34.58 # wtf? I thought putting functions into a .a would stop name collisions with the main binary? 03.35.11 # stupid skip_whitepace() being in both 03.35.46 # its just formatted however sandisk did it 03.36.39 # http://www.sdcard.org/consumers/formatter_3/ 03.36.44 # try that 03.39.22 Join funman [0] (~fun@rockbox/developer/funman) 03.41.54 Quit Luca_S (Quit: CGI:IRC (EOF)) 03.43.06 # i got immense speed gains by using the sd.org formatter - not only with sd cards and the like, but also CF and sony memorystick 03.45.51 Quit steve|m (Ping timeout: 276 seconds) 03.46.17 # FWIW, cowond2 has been checked to work with eabi but noone committed the change yet 03.47.01 Join WilliamC [0] (~WilliamC@75.110.58.61) 03.47.40 # funman, if you havent seen, its confermed that its 37 that breaks sd card support 36 works, and changing the clock didnt work :( 03.47.47 # So, uh, how do I report a bug in a daily build? 03.48.32 # AzureSky: ok 03.48.48 # http://forums.rockbox.org/index.php?topic=25104.0 03.49.33 # Themes no longer work on my Sansa e200 03.49.53 # update them 03.49.53 # Well, they don't work when playing music 03.50.37 # Doubt that will hjelp 03.50.39 # help 03.50.56 # why do you doubt that? 03.51.16 # All my themes worked until just a few days ago. 03.51.24 # Including the default. 03.51.25 # you know they changed the theme format dont you 03.51.41 # so what you're saying is that because something was up to date in teh past, it can't be out of date in the future? 03.51.46 # :) 03.51.52 # Up to date 3 days ago 03.52.11 # saratoga: trying flac @44.1kHz 16 bits (dunno about the quality) on clipv2 03.52.29 # funman: i just used the test_file flac and apes 03.52.45 # i also noticed one or two glitches playing mp3s, but i'm not sure if I was imaging things 03.52.55 # the APE ones were really obvious though since the decoder did not catch the error 03.53.03 # and just played loud static 03.53.03 # the same thing happened to me for mp3 today 03.53.07 Join krazykit [0] (~kkit@206.183.185.8) 03.53.43 # btw which target did you use? 03.53.47 # I install the daily build on a daily basis. 03.53.53 # clipv2 03.53.55 # it might be different: fuzev1/e200v2 have codec buffer in DRAM and all the others in IRAM 03.54.37 # considering the µSD bug on fuzev2 and the problems I had with PLLA@384MHz on clip+ i think we should revert the PLL change for AMSv2 to rule out problems with SD 03.56.11 # for SD i tested with test_disk on fuzev1/fuzev2, with µSD and internal, and with write&verify and speed test 03.56.57 # last time i had tried such a change it crashed quite fast but i supposed since then we had removed the last writing bugs from the drivers 03.57.31 # Also, I have it playing from my folder on my Sansa E200 but it doesn't seem to give me much variety. 03.57.47 # funman: test_disk gave no errors 03.57.52 # so i'm not sure what to make of it 03.58.05 # Is there to randomize it more? 03.58.13 # flac plays fine so far here on clipv2, i'll just revert the PLL change and let's see if we still see bugs 03.58.15 # Is there a way to randomize it more 03.58.38 # AFAIK its all ready completely random so you can't get more random then that 03.58.58 # So, why isn't it playing some songs? 03.59.08 # press next a random number of times, at random intervals 04.00.12 # WilliamC: random playback doesn't mean it'll play every song ... 04.00.19 # thats actually sort of the opposite of random :) 04.00.41 Join steve|m [0] (~steve@p4FD45CD4.dip.t-dialin.net) 04.00.41 # saratoga: shuffle does play everything... 04.00.48 # Just in a random order 04.01.07 # New commit by 03funman (r26979): Revert r26937 (as3525v2: use 248MHz PLL) ... 04.01.13 # yeah but theres no promise it'll ever play every song :) 04.01.26 # yes there is 04.01.31 # unless you stop it 04.01.34 # oh you mean shuffling a playlist? 04.01.57 # Is there another random option? 04.02.02 # IIUC playback settings -> shuffle does just that 04.02.20 # repeat shuffle? 04.02.25 Quit kramer3d_ (Ping timeout: 240 seconds) 04.02.45 # or does that just shuffle the current folder if i select it from the quickscreen 04.03.05 # r26979 build result: All green 04.03.05 # i assume not, since theres both shuffle and repeat shuffle 04.03.47 # TheSeven: i think i have posted a patch which aligned fat stack buffers some time ago, but a simple cache strategy might be worth 04.03.51 # repeat shuffle will still shuffle the whole playlist before playing any song twice 04.04.04 # why does the clip+ quick screen show "show files" twice? 04.04.04 # unless that song was in the playlist twice, in which case it wont be played a 3rd time 04.04.21 # Man, some of these themes suck 04.04.26 # so whats the difference between shuffle and repeat shuffle? 04.04.26 # because if an item is empty it uses the opposite item 04.04.28 # WTF, Screamiing Oprah 04.04.29 # saratoga: same on clipv1 (no idea why) 04.04.52 # a friend of mine asked me to ask if theres any chance of ading .pla playlist support(the playlists you can make using rclick in windows explorer or with alot of tools for devices like the fuze) 04.04.57 # saratoga: shuffle will shuffle the current playlist and stop, shuffle repeat will reshuffle at playlist end 04.05.07 # it is redundant and iirc there is a patch to reove it 04.05.08 # ah that makes sense 04.05.14 # AzureSky: current build should detect µSD fine on fuzev2 04.05.26 # ok i will giveit a test :D 04.05.28 # AzureSky: no plans for it 04.05.34 # AzureSky: there is a patch to convert pla t m3u 04.06.23 # ah didnt see one, it run on the device itself? 04.06.41 *** Saving seen data "./dancer.seen" 04.06.45 # i just use createM3U then edit the ones that are for multi folders 04.07.21 # saratoga, you're wrong 04.07.24 # one note, m3u/m3u8 dont work if you ad both sd card and internal memory items last i tested, but pla file do work 04.08.00 # I have a bug to report 04.08.39 # saratoga: btw about embedded art i think ucchan has posted a patch on flyspray 04.08.57 # yeah but it wasn't suitable 04.09.09 # I'll just purge the entire .rockbox folder. 04.09.57 Quit funman (Quit: free(random());) 04.11.07 Quit obo (Ping timeout: 265 seconds) 04.11.48 # ah heres the playlist converter: http://www.rockbox.org/tracker/task/6884 04.12.40 # but do the coverted playlists work on combine internal and external memory tracks? 04.13.21 # and yes, the new build does the trick for sd support :D 04.13.25 Quit dfkt (Quit: -= SysReset 2.53=- Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.) 04.14.13 Join Barahir_ [0] (~jonathan@frnk-590fcabd.pool.mediaWays.net) 04.14.22 Join webguest02 [0] (www-data@giant.haxx.se) 04.15.22 Quit webguest02 (Client Quit) 04.17.36 Quit Barahir (Ping timeout: 265 seconds) 04.19.47 Quit togetic (Ping timeout: 260 seconds) 04.20.27 # How do I save my dynamic playlist? 04.20.52 # Everything I do either moves the cursor or adds/deletes a letter 04.25.15 Quit binaryhermit (Read error: Connection reset by peer) 04.25.26 Quit efyx (Remote host closed the connection) 04.25.31 Join binaryhermit [0] (~binaryher@adsl-99-141-184-240.dsl.emhril.sbcglobal.net) 04.25.50 # DAMN 04.26.36 # Also, saratoga, wrong wrong wrong wrong wrong! 04.26.52 Join kramer3d [0] (~kramer@unaffiliated/kramer3d) 04.28.06 # I guess I'll just have to wait for most of my favorite themes to get updated. 04.28.47 # WilliamC: ? 04.29.10 # The themes are still broken, actually all the themes but the default are broken. 04.29.23 # which themes are these? 04.30.15 # WilliamC: there is an updater for the skin syntax change. 04.30.39 # black and blue glass, cabbie plus, cabbie v2, Vision, Sentinel 04.31.38 # cabbie v2 works. 04.31.41 Join kramer3d_ [0] (~kramer@unaffiliated/kramer3d) 04.32.16 # WilliamC: where/when did you get them from? 04.32.25 # The utility 04.32.37 # Installation utility 04.32.52 # http://www.rockbox.org/wiki/RockboxUtility#Download 04.33.44 Join togetic [0] (~togetic@unaffiliated/ibuffy) 04.34.19 Quit pixelma (Disconnected by services) 04.34.19 Join pixelma_ [0] (quassel@rockbox/staff/pixelma) 04.34.24 Quit amiconn (Disconnected by services) 04.34.26 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.34.27 # None of the themes I have installed were updated recently. 04.34.35 Nick pixelma_ is now known as pixelma (quassel@rockbox/staff/pixelma) 04.34.44 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.35.00 Join DerPapst1 [0] (~Alexander@p4FE8F654.dip.t-dialin.net) 04.35.15 # WilliamC: other half of my question :) 04.35.34 Quit kramer3d (Ping timeout: 258 seconds) 04.35.44 # Cabbies V2 works but I don't remember installing that, it must have come with the build 04.37.13 Quit DerPapst (Ping timeout: 265 seconds) 04.37.43 # How do you save playlists? 04.37.53 # you could try a fresh install of rockbox. 04.38.02 # AzureSky, I just did 04.38.05 # WilliamC: You can fix them with the skinupdater - a windows version can be downloaded here - http://forums.rockbox.org/index.php?topic=24907.msg168423#msg168423 04.38.43 # or probably just download the updated versions 04.38.57 # They don't exist though 04.39.10 # have you checked? 04.39.16 # yeah 04.39.16 # IIRC almost all were updated 04.39.30 # did you check poorly? 04.39.33 # http://themes.rockbox.org/index.php?target=sansae200 04.39.56 # Next you're going to be asking me if it's plugged in. 04.40.09 # AFAIK all themes on that site should be updated 04.40.13 # did you check any of them? 04.40.36 # YES I DID GOD DAMN IT 04.40.59 # which one? I'll try it 04.41.04 # have to run in a moment though 04.41.05 # rockbox utility seems to download the old, fubar versions of the themes rather than the new fixed version 04.41.14 # in my experience 04.41.18 # Ok 04.41.21 Join Piki [0] (~Piki@unaffiliated/piki) 04.41.28 # The website says use the utility though 04.41.44 # if you download the themes manually you get the fixed versions 04.41.46 # i only have a couple minutes, so if you want help, hurry up 04.41.51 # i use the svn version 04.41.57 # again, in my experience 04.42.14 # dosnt support skins for fuzev2 so i have to pretend its a v1 :P 04.42.41 # I cannot find the skins I'm using 04.43.20 # I am confused. 04.43.40 # do they show up in rbutil? 04.44.10 # yeah 04.44.26 # so which are they? 04.44.33 # The vision ones 04.44.33 # WilliamC: maybe try the latest svn version of Rockbox Utility - http://tinyurl.com/rbutil-dev 04.44.45 # Sand, Wave and Wood 04.44.49 # cabbie plus? 04.44.52 # oh 04.45.49 # well Wave and Wood doesn't appear to have come from the theme site, so no surprise its not updated :) 04.46.25 # I'll use that update utility I guess 04.46.44 # which ones were you saying didn't update on the theme site? 04.47.08 # The ones I'm complaining about aren't listed 04.48.00 # Actually Black n Blue Glass is listed 04.48.04 # LEt me see 04.48.37 # That works 04.48.50 # So, the utility is giving me old themes? 04.49.05 # cabbie plus is, and it works too from the theme site, but rbutil installs the old one 04.49.11 # let me see if a newer rbutil fixes that 04.49.43 # Sorry, I just get angry when I feel that people are treating me like an idiot. 04.50.31 # I think I developed that from unsatisfactory tech support calls where they try to avoid doing any actual support. 04.51.09 # yeah the SVN installer works fine 04.51.15 # ok, thanks 04.51.20 # but the current release still installs themes for the old syntax 04.51.30 # hello, just did the manual install of Rockbox on a Fuze v2 (I know, it's an unstable port, but was working fine when i first installed it). after turning on the Fuze, Rockbox loaded normally like it did on my Fuze v1. i plugged in the v2 without shutting it off, and the screen went blank. i tried a soft reset (holding the power button in the on/off position for up to a minute). i also tried putting the power button in the hold position and plugging in while 04.51.32 # holding the submenu/playlist button, and tried the same thing again except that i held in the center/select button 04.51.46 # sorry for the long post, but i was hoping for a bit of help 04.51.47 # saratoga, how do I save the dynamic playlist? 04.52.17 # WilliamC: no idea 04.52.44 # Shame there is no enter key and the select key just enters in new letters. 04.53.11 # Piki: if holding power for a long time doesn't work, i think you have to let the battery run out 04.53.38 # Holding the power button normally works. 04.54.07 # First time I had a kernel panic, I followed suit. 04.54.10 # im not worried if i brick the fuze, i paid for 2 year geeksquad warr that will replace it no questions asked :P 04.54.25 # http://download.rockbox.org/daily/manual/rockbox-sansafuzev2/rockbox-buildch4.html#x7-420004.1.3 04.54.32 # AzureSky, those warranties are a bunch of BS, btw. 04.54.34 # saratoga: any guesses as to how long a fully charged batttery will take to discharge? or will i just have to guess? 04.54.37 # if those keys are wrong, post a flyspray ticket and someone will probably fix it 04.54.57 # funny, i have used it many times willy and its worked eveyr time on every device i have bought at bb 04.54.58 # depends what it was doing when it crashed, but the battery lasts about 20 hours fully charged playing music, so thats a rough estimate 04.55.11 # AzureSky, if you want to get them to actually fix or replace anything, you'll get the urge to ram the phone up their rectum eventually. 04.55.14 # Piki, up to 3 or so days 04.55.44 # AzureSky: for a blank screen? wow, i thought it would be longer 04.55.50 # willy, u go into store, they take the player give you a card with the players value when you bought it on it, you go pick ur replacement 04.56.28 # or u can do a strait swap in store, i have done this many times, never had a problem 04.56.30 # AzureSky, oh, well, when I had an extended warranty they had me deal with a call center first, they tried to find reasons to not help me. 04.56.40 # Pike thats what the Wiki says for time 04.56.47 # This was CircuitCity 04.56.57 # an bestbuy isnt like that 04.57.09 # they honestly just dont give a crap 04.57.22 # AzureSky: not to be picky, but i'm not based on a street, i'm based on a "Piki" person 04.57.36 Quit TheSeven (Ping timeout: 264 seconds) 04.58.04 # an option that works well is to get a squaretrade warr on stuff, they replace it even if u smash it with a hammer :P 04.58.10 # rockbox-community is a better place to chat about off topic things 04.59.52 Quit saratoga (Quit: Page closed) 05.00.46 Join HANSi [0] (~CLD@85.26.232.134) 05.02.52 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 05.02.58 Quit saratoga_ (Quit: Page closed) 05.10.03 Part WilliamC ("Leaving") 05.15.34 Quit HANSi (Read error: Connection reset by peer) 05.20.28 Nick CGL_emo is now known as CGL_party (~CGL@190.207.202.226) 05.23.40 Part Piki ("Konversation terminated!") 05.29.35 Quit t0rc (Remote host closed the connection) 05.42.00 Join HANSi [0] (~CLD@85.26.165.140) 05.53.07 Quit anewuser (Ping timeout: 260 seconds) 06.06.45 *** Saving seen data "./dancer.seen" 06.07.55 Join kramer3d [0] (~kramer@unaffiliated/kramer3d) 06.08.20 Nick kramer3d is now known as destiny (~kramer@unaffiliated/kramer3d) 06.09.28 Nick destiny is now known as Azaroth (~kramer@unaffiliated/kramer3d) 06.12.09 Part HANSi ("Leaving") 06.19.41 Join JesusFreak316 [0] (www-data@giant.haxx.se) 06.20.10 Quit JesusFreak316 (Client Quit) 06.37.50 Quit panni_ (Read error: Connection reset by peer) 06.49.05 Join hebz0rl [0] (~hebz0rl@dslb-088-067-195-007.pools.arcor-ip.net) 06.49.31 Quit Azaroth (Quit: Leaving) 06.55.58 # saratoga: There are still quite a few themes missing, and a few pass checkwps, but have invalid syntax. 06.56.25 # Updating the themesite didn't really go that well IMO 06.59.16 Quit mc2739 (Ping timeout: 276 seconds) 07.00.08 # There's 4 or 5 missing from Nano 1/2G alone, I really should look which ones they are, but I haven't had much luck trying to get one theme updated, let alone several. 07.00.32 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 07.00.32 Join BHSPitMini [0] (~BHSPitMon@ppp-70-243-200-93.dsl.rcsntx.swbell.net) 07.01.11 # seems most of the themes for my fuze use 24hr day on the playing screen, but every other screen they use the setting i choose(12hr) 07.01.51 # I ened up updating mine myself, which is ok for me but I don't want to go behind an authors back and re-submit a theme. 07.02.00 # AzureSky: You can edit that easily. 07.02.23 # can u give me a hand only 2 themes i use both have the issue 07.02.29 # It just means the theme forces 24hour instead of using a 12/24 hour conditional (which is poor form IMO) 07.02.48 # The manual can give you a hand... 07.02.53 # i can deal with 24 but i just dont want to :P 07.04.36 # Find the clock line in the WPS and replace it with "%?cf<%cH:%cM|%cI:%cM%cP>" 07.05.13 # that line (I'm pretty sure I got it right...) will respect the user setting for 12/24 hour 07.06.13 # It will also pad the hour/minute with a 0 so it doesn't mess up alignment. 07.06.33 # :) nice :D 07.11.41 # working on it 07.15.45 Join Horschti [0] (~Horscht2@xbmc/user/horscht) 07.18.26 Quit Horscht (Ping timeout: 240 seconds) 07.20.57 # AzureSky: If you really get stuck, pastebin the wps and I'll fix it up. 07.21.07 # Just, at least have a go first ;) 07.21.26 # pastebin? 07.21.29 # argh... S_a_i_n_t forgot to close the bold section. 07.21.37 # http://rockbox.pastebin.ca/ 07.25.52 # http://rockbox.pastebin.ca/1886862 07.26.34 # got 1 other that i need clock help on, edited like you showed and it didnt work, removed clock from the playing screen :P 07.27.05 # New commit by 03mc2739 (r26980): FS#11418 by Peter Lecky: Slovak language update 07.28.21 # http://rockbox.pastebin.ca/1886863 07.28.47 # r26980 build result: All green 07.32.28 Quit storm` (Ping timeout: 260 seconds) 07.35.30 # AzureSky: http://rockbox.pastebin.ca/1886865 07.35.32 Join storm` [0] (~lol@ip98-179-182-180.ri.ri.cox.net) 07.35.44 # * S_a_i_n_t sees no reason why this code should not work. 07.36.06 # thanks 07.36.12 # will test now 07.36.15 # unless you included the ""s when you editied it? 07.36.22 Quit binaryhermit (Ping timeout: 264 seconds) 07.36.51 # not that i know of but i just cleaned out a stack of themes i dont like, i try and keep things light 07.40.41 Join binaryhermit [0] (~binaryher@adsl-99-141-184-240.dsl.emhril.sbcglobal.net) 07.41.04 # waiting for refresh.....stupid fuze refresh of db every time i edit a file :P 07.42.21 # worked great :D 07.42.32 # i see what i did wrong to :) 07.42.55 # i suck at editing files that look like gibberish :P 07.45.08 # i gotta get a buddy to remote in again and get my cygwin to work again, so i can compile latist build with saratoga's volume patch 07.45.32 # what's wrong with your CygWin? 07.45.41 # it can be a PITA, but is easy to setup. 07.46.52 # it was working last night now it keeps saying its missing the arm-elf-eabi-ld 07.47.06 # Just delete the Gygwin folder completely, reinstall according to the wiki, don't download the toolchains though, checkout the rockbox source, run rockdev.sh, done. 07.47.34 # Oh, Hmmm...ignore that then, that's overkill for that fix. 07.47.47 # no clue how to run that to be honest im not at all a programer 07.48.07 # removing the toolchain and re-running rockboxdev.sh should fix that. 07.48.13 # i use to be able to script for sphere UO server emulator a bit thats it :P 07.48.33 # how do i run the rockboxdev.sh? 07.48.43 # but, even that is probably overkill compared to what is probably needed to fix it. 07.48.51 # one sec. 07.49.28 # just cd to "tools" then "./rockboxdev.sh" 07.49.29 # i SUCK at this stuff, if i had an acct like my buddy with citrix easy support i would let you remote in and do it :P 07.51.26 # its doing its thing now 07.51.31 # hope this works :) 07.52.10 # i thought i was done using commandline all the time when i moved to windows 2000 years ago :P 07.52.11 # It should do, you told it to build arm-eabi by inputting "e" I take it? 07.52.45 # did the one that listed sansa and e as well 07.53.23 # one nice thing about having a 6 core, even when doing stuff like compiling i never endup being bogged down :D 07.53.47 # *cough* /topic *cough* 07.53.55 # sorry 08.06.47 *** Saving seen data "./dancer.seen" 08.08.40 # ok, quick question, how do i go about using satatoga's volume patch? 08.30.44 # ok, 1 more what is the command to update the source i already have to latist rather then redownload the whole thing again? 08.30.55 # "svn update" 08.31.09 # seems to simple no? 08.31.12 # *too 08.31.34 # yeah that is to simple 08.31.45 Quit leavittx (Read error: Connection timed out) 08.32.02 Join mitk [0] (~mitk@chello089078013092.chello.pl) 08.32.07 # "svn --help" will tell you other possibly commands. 08.32.16 Join leavittx [0] (~leavittx@89.221.199.187) 08.32.19 # adding "--help" to almost anythng works. 08.32.51 # do i need to add a revision number or url to the "svn update" command? 08.33.33 # nm its working :D 08.33.44 # "svn update" will always pull the latest revision. 08.33.58 # even "svn up" wil work. 08.34.42 Join ast[1] [0] (~astreaz@CPE-121-217-6-3.lnse1.cht.bigpond.net.au) 08.35.43 Quit ast[1] (Client Quit) 08.37.30 # * S_a_i_n_t points AzureSky to: http://www.rockbox.org/wiki/DocsIndex#For_Developers 08.37.48 # it answers all the basic "How do I...?" development questions. 08.50.53 Join Highlander [0] (~Highlande@mek33-4-82-236-45-205.fbx.proxad.net) 09.05.55 Quit kramer3d_ (Ping timeout: 260 seconds) 09.26.28 Join bmbl [0] (~Miranda@unaffiliated/bmbl) 09.28.40 # New commit by 03jdgordon (r26981): fix the viewport tag [arams 09.30.23 # r26981 build result: All green 09.38.47 Join Kitr88 [0] (~Kitar_st@89.142.60.25) 09.42.25 Quit Kitar|st (Ping timeout: 276 seconds) 09.43.15 Quit Kitr88 (Ping timeout: 248 seconds) 09.43.43 Join flydutch [0] (~flydutch@host110-154-dynamic.14-87-r.retail.telecomitalia.it) 09.48.43 Join Kitar|st [0] (Kitar_st@BSN-143-111-251.dial-up.dsl.siol.net) 09.50.42 Join stoffel [0] (~quassel@p57B4C717.dip.t-dialin.net) 09.57.14 Join Rob2223 [0] (~Miranda@p4FDCA1FA.dip.t-dialin.net) 10.00.37 # * JdGordon spots a rather bad bug in the legacy skin parser :/ 10.00.47 Quit Rob2222 (Ping timeout: 265 seconds) 10.06.49 *** Saving seen data "./dancer.seen" 10.09.23 # I assume noone noticed that sharing fonts between skins doesnt actually work? 10.09.48 Join petur [0] (~petur@rockbox/developer/petur) 10.09.49 # they will work, but the font will be loaded twice! 10.11.29 Quit TheSeven (Ping timeout: 272 seconds) 10.13.07 Quit binaryhermit (Quit: Leaving) 10.13.53 # sharing fonts between skins - what do you mean with that? 10.17.00 # if you load the same font in more than one skin, the font should only load once 10.17.13 # I just noticed that is almost certainly not happening 10.31.56 # I thought I noticed that by looking at the skin buffer...but I wasn't sure, nor could I confirm it. 10.41.44 Join hamish_ [0] (~hamish@119.224.50.74) 10.41.54 Quit hamish_ (Client Quit) 10.44.13 Join ender` [0] (krneki@foo.eternallybored.org) 11.03.23 Quit mc2739 (Read error: Operation timed out) 11.05.03 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 11.09.55 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 11.37.01 Join ender1 [0] (krneki@foo.eternallybored.org) 11.37.19 Quit ender` (Disconnected by services) 11.37.23 Nick ender1 is now known as ender` (krneki@foo.eternallybored.org) 11.39.57 # * S_a_i_n_t wonders where to start to try and make "make voice" smart enough to do "nothing to be done for `all`" instead of cimpiling a voicefile even if no changes were made... 11.50.24 Join Jerom [0] (~Jerom@79.132.53.242) 11.51.30 Join andromedea [0] (~manzanita@ip68-104-236-55.ph.ph.cox.net) 11.58.35 # I read through the links in the topic and can't help myself. I'm trying to install rockbox on my sansa e200 and keep getting "Bootloader mismatch! Aborting" 11.59.39 # andromedea, is it an e200 or and e200v2? 11.59.48 # e200 12.00.15 # I think you get this message when you installed the correct bootloader but the wrong rockbox main firmware 12.01.21 # What rockbox version exactly are you trying to install? I could have a try with the same version on my e200. 12.04.06 # Here's the trick: it's potentially an R. I bought it refurbed, and it said "rhapsody" on it, but performed no rhapsody functions. 12.05.05 # Sorry, I'm not familiar with the installation procedure for the rhapsody versions 12.06.51 *** Saving seen data "./dancer.seen" 12.18.21 # andromedea: did it just say "Rhapsody" on its back plate or so? Sandisk is known to assemble those together in different ways... What were the USB mode settings in the original firmware called? 12.27.51 # it just says rhapsody on the back plate. ... and now it won't even turn on. 12.29.50 # usb setting were msc/mtp 12.30.09 # what is producing this "Aborting!" message? Rockbox Utility? 12.30.17 # yes 12.30.48 # oh sorry, then I gave the wrong answer to your first question, I thought it was the bootloader complaining 12.31.23 # ok, then then nothing should have been written to the player. 12.31.32 # then it's no Rhapsody as far as I know. The USB settings are called something like "Plays for sure" or somesuch 12.32.00 # I figured 12.32.41 # v 1.02.24 12.32.44 # have you already tried resetting the player? I.e. hold Power until it turns off, then power it up again? 12.32.58 # yes 12.33.07 # bluebroth3r: the error "bootloader mismatch" sounds a bit like there already is a Rockbox bootloader on it, or not? 12.34.13 # google turns up depressingly little 12.34.17 # no, that is an internal check of the downloaded file 12.34.52 # after the bootloader has been downloaded it gets its version information checked. 12.35.02 # andromedea: have you saved the system trace of Rockbox Utility? 12.35.51 # do we currently allow %xd() and %vd() to reference a not yet loaded image/viewport? 12.36.04 # i.e before the coresponding %xl/%vl ? 12.36.19 # JdGordon: Yes 12.36.28 # I'm not following 12.36.32 Join DataGhost [0] (~dataghost@17-18-ftth.onsnetstudenten.nl) 12.36.32 Quit DataGhost (Changing host) 12.36.32 Join DataGhost [0] (~dataghost@unaffiliated/dataghost) 12.36.40 # S_a_i_n_t: ok thanks 12.36.42 # bugger :p 12.36.57 # sorry, I just answered the question :P 12.37.02 # andromedea: after that error appears there should be a "save log" button in the log windows. Did you use that? 12.37.30 # JdGordon: %Vd before the %Vl was said to be a must with the first implementation 12.37.48 # ok, yeah, just making sure the new parser owuldnt break that 12.37.55 # easy enough to work around it 12.38.18 # I find it good practice to load before the call, but it isn;t necessary. 12.38.38 # if not, have you closed and opened Rockbox Utility in the meantime? 12.39.14 # fail.log is empty 12.39.23 # and yes, i have 12.39.31 # empty? That's strange. 12.39.36 # is Rockbox Utility still running? 12.39.42 # yes 12.39.48 Quit cjcopi (Read error: Operation timed out) 12.40.05 # ok, can you go to the Help / Troubleshooting / System Trace menu? It should show the most recent trace 12.40.57 # http://pastebin.org/344983 12.42.55 # you have selected the c200 as player but it's in fact an e200 12.43.21 # installing the wrong bootloader would cause serious problems, so bootloader installation verifies this and refused to install the wrong bootloader. 12.43.24 # jesus 12.43.34 Quit JdGordon (Quit: Leaving.) 12.43.35 # what an idiot 12.43.36 Quit JdGordon| (Remote host closed the connection) 12.43.40 # (this at least works for e200 vs c200, it's a bit different for other players) 12.43.51 # please try again with the correct player setting :) 12.45.25 # i just want to point out that "c" and "e" bear a strong resemblance at 3am 12.46.09 Join halmi [0] (~netbook@80-123-38-102.adsl.highway.telekom.at) 12.46.30 # * S_a_i_n_t hands andromedea a screen magnifier ;) 12.47.08 # * pixelma blames Sandisk ;) 12.47.13 # don't worry, such mistakes happen. Though autodetection should have worked done the correct thing for you ;-) 12.50.06 # oh good, iwas hoping this would fix the jumpy wheel thing, but it didn't 12.50.43 Join efyx [0] (~efyx@lap34-1-82-225-185-146.fbx.proxad.net) 12.52.41 # thanks for the elp guys :) 12.58.56 Join pamaury [0] (~quassel@p5DDEF6F6.dip.t-dialin.net) 12.59.04 Quit pamaury (Changing host) 12.59.04 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 13.03.43 # hoo boy, now my computer doesn't recognize the sansa 13.05.05 # what operating system does your computer run? 13.05.16 # pixelma: Building manuals automatically might be desirable, but there is at least one fundamental problem 13.05.44 # windows 7 13.06.14 # Building them only after commits to manual/ isn't enough, because afaiu the manuals also use the config/ stuff to figure out features 13.06.23 # They also use tools/configure. 13.06.50 # But building manuals after every commit is overkill, imo 13.07.32 # andromedea: weird... your Sansa and its microSD slot should get a drive letter in explorer, I'm not aware of USB problems with Windows7 13.08.07 # * S_a_i_n_t still needs to turn off HID on the Nano1g sometimes on Win7 13.09.15 # amiconn: I thought of that too (the features parsing), but it will still be much better than now and if a commit to features.txt will break a manual then it needs a commit to manual/ to fix it anyway (or to features.txt again) 13.11.32 # The features file is generated as part of the build (btw, that's the reason why a manual build as well as a voice build needs the target crosscompiler) 13.11.38 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 13.12.18 # So if a code change that changes features breaks a/the manual(s), you won't notice if it doesn't trigger a manual build 13.13.04 # but now you sometimes even won't know if a manual commit breaks a manual 13.13.40 # you have to wait for the next day and check (and not forget in the meantime) 13.14.18 # Since we don't have automated manual builds now, I'd expect the committer to test more thoroughly before commit 13.14.47 # I test a lot but still overlooked one manual last time 13.15.19 Join Buschel [0] (~~andree@p54A3D2C1.dip.t-dialin.net) 13.15.44 # I'm not saying automated builds are bad - but defining the conditions which should trigger a build seems to be complicated 13.16.57 # Btw, the automated binary builds have the same problem, albeit to a lesser degree 13.17.53 # and as you said yourself, manuals can break even when committing something to the rest of the code which happened last time with some hotkey enabling. Then almost no-one notices 13.18.33 Join t0rc [0] (~t0rc@unaffiliated/t0rc/x-5233201) 13.19.00 # Another problem is scanning the build output for errors, given the ton of messages a manual build produces 13.19.38 # IMO doing commits on changes to manual/ would already be a great help - or another idea discussed sometimes: a frontend that lets committers trigger a new daily manual in case it was broken 13.19.47 # This output contains numerous 'warning' and 'error' messages which are meaningless - but some will be real 13.20.17 # This is different from the main builds 13.21.12 Nick Horschti is now known as Horscht (~Horscht2@xbmc/user/horscht) 13.21.17 # in my experience it'll do with checking if it compiles at all and not using non-stop mode. On an error that really breaks a manual, the build process stops (and asks you what it should do) 13.21.42 # Yes, and that's even worse 13.22.01 # eh, why? 13.22.07 # You cannot automate that - if you have a manual that doesn't build, the process won't end 13.22.31 # Nobody is there who could answer that request. You could kill the process 13.22.56 # But you won't see what messages it generated. Logging all of them is not an option I'm afraid 13.23.16 # So all you get is a simple yes/no answer - did it generate an output file or not? 13.24.12 # with non-stop mode building should break on errors, not ask for user input 13.24.37 # the problem is when you try to manually interrupt building because LaTeX will then go into interactive mode 13.24.44 # Yeah okay - that still leaves the problem that you don't get to see the messages 13.24.46 # bluebroth3r: yes, but how do you find the "offending" error then? 13.25.10 # pixelma: seems like those guys managed to get an output parser done: http://vim-latex.sourceforge.net/screenshots/compilation-error.png 13.25.34 # I was thinking in looking into it in the hope to generate an output filter script 13.25.51 # btw, the output itself is also written into the log file in the build folder. 13.26.47 # one option to address the dependency issue would be to automatically generate dependencies for the manual, and trigger a rebuild if any of those files changes. This will of course fail if the dependencies change, but IMO this would be a minor issue 13.26.52 # Did you compare the log size of a manual build and a main build? 13.27.34 # no, why? 13.28.11 # I know LaTeX prints heaps more of (partly unimportant) stuff 13.28.21 # for upload purposes I guess 13.28.39 # and for people to look through 13.29.29 # that's the reason why I wanted to try getting a parser for the log files done 13.31.41 # 66kB for this somewhat outdated manual build log file 13.31.41 Part andromedea 13.31.47 # and if Zagor or someone else won't fix whatever is broken in the voice and manual daily build script then we won't have manuals from tomorrow on or so I guess :\ 13.32.01 # wouldn't consider that too bad. It's noticably worse than the build logs of course 13.32.50 # we won't have manuals anymore? Aren't the old ones kept in case updating fails? 13.33.03 # if there is an error in it besides the warnings in non-stop mode how will you find it 13.33.51 # bluebroth3r: not that I've seen the last few times manuals were broken long enough (longer than 3-4 days recently) 13.36.09 # pixelma: ouch, that's bad. If things fail I can build a round of current manuals and upload them to my webspace though. 13.37.34 # pixelma: grep the log file for lines starting with ! 13.38.39 # hmm, might even be sufficient to filter the LaTeX output 13.39.15 # for normal filtering that is 13.39.17 # maybe that could be done on the build client side before uploading the log? 13.40.52 # I'm thinking about filtering the stdout messages for that. Would make the output much more useful. 13.41.12 # will hide Overful / Underful messages though, but I don't think anyone cares about them anyway. 13.43.50 Join webguest59 [0] (www-data@giant.haxx.se) 13.44.34 # the only thing I "use" them for is to see if compiling still goes on ;) 13.44.35 Quit webguest59 (Client Quit) 13.46.30 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 13.50.10 # I'd at the least like a table that shows whether each manual built during the last round 13.50.39 # amiconn: It just isn't feasible to always catch all errors 13.51.14 # pixelma: http://pastebin.com/7JRRefei 13.51.20 # Speaking for myself I always build lots of different ones, but they can slip through and at the moment there is no easy way to see if they are broken or not 13.51.49 # * bluebroth3r should dig out his old buildall script for the manuals 13.52.27 # pixelma, AlexP: you're aware that the WPS tags in the manual haven't been updated to the new syntax yet? 13.52.40 # bluebroth3r: I'm about to commit that 13.52.57 # AlexP: the tags? Nice. 13.53.01 # Currently test building 13.53.46 # Is there any way in the tagmap tables to break the first column but still remain in a cell? Some of the tags are so long that they leave about 4 letters for the explanation 13.54.13 # AlexP: IIRC \newline did that. Not completely sure though 13.54.22 # thanks, I'll try 13.54.40 # \newline works great in button tables for that 13.54.52 # CustomWPS hasn't been updated either and I thought JdGordon would at least do that 13.55.10 # I've also added multifont 13.55.51 # pamaury: I had some thoughts about the drive cache tonight 13.56.15 # how should we deal with write accesses? 13.56.41 # should they lock out other accesses to that sector until the sector gets committed? should they read the old state? should they read the new state? 13.56.52 # do we need an "exclusive read" mode? 13.57.29 # hmmm, doesn't seem to work 13.58.19 # what happens with pre-existing read handles to a sector if it gets opened for writing? allocate a new buffer for that? 13.58.25 # or block until the read handles are closed? 13.58.57 # wtf? Why does the grep filtering don't work on the first run in a clean folder? 13.59.51 # or even panic in that case? 14.00.18 # (can it ever happen that a sector is being written while it's opened for some file/dir? 14.02.43 Join playing-the-fool [0] (~zic@lin67-4-78-239-42-148.fbx.proxad.net) 14.06.55 *** Saving seen data "./dancer.seen" 14.06.56 # I was wondering what happens with the manual and the wiki regarding wps syntax. 14.07.10 # No \newline doesn't work, it just eats the space 14.07.11 # what happens if someone has the release build? 14.07.21 # (and wants to check wps syntax) 14.07.22 # They use the release manual 14.07.29 # AlexP: what? 14.07.42 Quit playing-the-fool (Quit: Ухожу я от вас) 14.07.43 # pixelma: r.e. \newline? 14.07.47 # yes 14.07.48 # aha...right, that's a bit of a facepalm on my part ;) 14.07.55 # * S_a_i_n_t creeps back into his corner 14.08.18 # pixelma: I have this: \config{\%V(x,y,[width],[height],[font])}\newline \config{\%Vf([fgcolour]) \%Vb([bgcolour])} & See section \ref{ref:Viewports}\\} 14.08.54 # * bluebroth3r figured it 14.09.02 # pixelma: I want a line break where \newline is, but all that happens is that I get "font])%Vf with no space 14.09.17 # what happens with just the space? 14.09.24 # The space is there 14.09.40 # i.e. ...font]) %Vf... 14.10.40 # I mean: doesn't LaTeX break the line on a simple space anyway if necessary (without the \newline) 14.11.13 # maybe there is a difference between the table environment for button tables and the one you are dealing with currently 14.11.37 # no, it doesn't break 14.12.11 # must be, I'll have a look what 14.12.54 Quit stoffel (Ping timeout: 265 seconds) 14.13.48 # is there any documentation on the source tree? 14.14.15 # what does go to common, what to drivers, and what's directly in firmware? 14.14.30 # are there any guidelines for this? 14.14.38 Join cjcopi [0] (~craig@charon.craig.copi.org) 14.15.25 Part Jerom 14.15.43 # pixelma: ah, found something: the LaTeX run can stop in interactive mode when doing the first run in an empty folder. That's because a different rule triggers first and is lacking $(LATEXOPTS) :( 14.16.20 # pixelma: that would be fair if I had touched it at all... 14.17.03 # TheSeven: what are you asking about in particular? 14.17.16 # I'm about to add a disk cache layer 14.17.26 # JdGordon: you did not change the WPS syntax - or what are you referring to? 14.17.33 # or rather sector buffer pool 14.17.34 # AFAIK there isnt any actual guidelines... whereever it makes sense 14.17.46 # and what *does* make sense? 14.17.46 # bluebroth3r: sorry, I can't follow 14.17.55 # pixelma: I meant because I hadnt fixed the doc at all that wasnnt fair 14.18.14 # it is a wiki after all... 14.18.23 # storage.c is in firmware, fat.c is in drivers, file.c, dir_uncached.c and dircache.c are in common 14.18.29 # pixelma: the Makefile for the manual has a bug. It requries running LaTeX several times (which is needed because of LaTeX way of breaking text). 14.18.48 # i don't really see any scheme behind this 14.18.57 # there probably isnt any 14.19.07 # however, the first run of LaTeX triggers a different Makefile rule. These also calls pdflatex, but fails to pass the $(LATEXOPTS) value thus not enabling nonstopmode. 14.19.13 # so that's just a "put it wherever you like"? 14.19.24 # what are those folders for then? 14.19.37 # so for this first run (which only gets triggered if the .aux file doesn't exist) building *can* end up in interactive mode 14.19.41 # why don't we just throw everything into a single one? 14.20.05 # * bluebroth3r wonders if there's a way to make LaTeX not break its output at 80 characters 14.20.07 # it probably made sense 5 years ago 14.20.22 # JdGordon: I didn't follow everything that had changed (which thing is which now) and since you invented it you have the best knowledge. Since you are not touching the manual at all and kept CustomWPS up-to-date the last times you changed things... 14.21.42 # TheSeven: sorry, I just saw you talked to me :) 14.22.23 # I would say that there are two different ways to do it: 14.22.48 # 1) Sector cache: a layer between storage api and actual storage api, you need to solve all these issues 14.23.27 # 2) Sector pool: just a specialized kind of malloc, we just need to use it instead of allocating on stack, no change in the storage layer 14.23.59 # New commit by 03theseven (r26982): Add a STORAGE_ALIGN_ATTR macro, similar to CACHEALIGN_ATTR, for consistency 14.25.06 # pamaury: I'd like to do something in between 14.25.41 # r26982 build result: All green 14.25.54 # TheSeven: how is this possible ? :) 14.27.42 # keeping it as simple as possible while at least re-using buffers for multiple read accesses to the same sector 14.28.10 # i'm wondering if it should be merged with the fat cache or not 14.28.27 # I would personally go for the first one because I'm not sure a sector "cache" is useful. We don't do much disk accesses so it's will basically be a cache miss on every read/write. The FAT is the only exception imo 14.28.56 # I might be proved wrong of course. 14.29.22 # New commit by 03theseven (r26983): Use STORAGE_ALIGN_ATTR for instead of hardwired alignment in the Nano2G FTL and NAND driver 14.30.16 # searching directories might have a few hits 14.30.52 # hm, that's right, but I *think* the fat_dir does caching by itself for directory scanning, let me check 14.31.01 # r26983 build result: 88 errors, 0 warnings (theseven committed) 14.31.06 # (anf there is dircache of course) 14.31.09 # it only has a single buffer for that 14.31.43 # yes, one buffer per dir, that's sufficient, it's sequential accesses 14.31.46 # i just think it can't hurt to keep recently used data around until to be able to re-use it until we need the space 14.32.40 # * S_a_i_n_t often wondered about the source subdirs, for someone like myself its a real PITA to find anything. 14.33.00 # No, it's just that a cache is more complicated than a simple pool 14.33.01 # there doesn't seem to be any rules defining where things should be placed. 14.33.19 # and, IMO, there should be. 14.33.33 # S_a_i_n_t: basically, on the least common ancestor of uses :) 14.33.40 # with exceptions :) 14.34.10 # New commit by 03theseven (r26984): Also define STORAGE_ALIGN_ATTR if STORAGE_WANTS_ALIGN isn't defined 14.34.15 # its "the exceptions" that confuse me :P 14.34.25 # TheSeven: so you would go for a api that allows you to read a sector and give you a handle to a buffer, that's right ? 14.34.54 # reorganising the code so everything was in its propper subdir would be a real PITA, but worthwhile. 14.35.03 # then creating rules, and sticking to them. 14.35.19 # S_a_i_n_t: what are the exception ? I can see the drivers/ one which has strange subdirs in it but that's all 14.35.31 # New commit by 03theseven (r26985): Fix misspelled STORAGE_WANTS_ALIGN in s5l8700/system-target.h. Also add PROC_NEEDS_CACHEALIGN. 14.35.44 # r26984 build result: All green 14.36.01 # Ok, I need to leave for a few minutes, continue to give your thoughts on the sector cache please 14.36.05 # what's the exact meaning of the "common" dir? 14.36.10 # things like rbutil for instance (a lesser example)..why is this split out? why not have it in tools? 14.36.11 # "common" between what exactly? 14.36.14 # is it not a tool? 14.36.39 # S_a_i_n_t: tools are build scripts and similar stuff 14.36.49 # if anything, it should be in util/ 14.37.08 # r26985 build result: All green 14.37.12 Quit Rob2223 (Quit: Rob2223) 14.37.31 # pamaury: yes, that's basically what I'm planning to do 14.37.37 # it's all just one big bloody mess! 14.38.24 Join stoffel [0] (~quassel@p57B4C717.dip.t-dialin.net) 14.38.26 # JdGordon: This is true. 14.38.28 # the question is just if the fat cache should be merged with that, so that it can use the currently-free sector buffers as additional cache. this means that we have to handle writes somehow of course, but that could be done in a similar way as the fat cache is doing it currently 14.38.35 # it may as well be one directory :/ 14.39.03 # At least then I'd know exactly where to look for things :P 14.39.25 # New commit by 03bluebrother (r26986): Apply LATEXOPTS to all LaTeX runs. ... 14.40.56 # r26986 build result: All green 14.41.06 # S_a_i_n_t: the common/ dir is a bit strange, I admit that. It's more a user interface to the firmware but yeah... 14.41.26 # TheSeven: if you do it this way, get rid of the fat cache, that's basically the same behaviour no ? 14.41.55 # yes, with some small additions 14.42.40 # you need the ability to lock buffers etc. 14.42.55 # yes 14.43.26 # and the ability to read without using a cache buffer also, when you already have a buffer 14.43.43 # and you know there is little point in caching 14.45.16 Join Rob2222 [0] (~Miranda@p4FDCA1FA.dip.t-dialin.net) 14.45.21 # IIUC there will always be only a single user for everything that may be written (either the FAT, a dir or a file) 14.45.24 # pixelma: can you give that change a try on cygwin? http://pastebin.com/4AUPGRuz 14.45.47 # S_a_i_n_t: anyway, the subdirs are mainly here to avoid having a big chunk of .c files, it's suboptimal but better than a plain dir imo 14.46.06 Join fdinel [0] (~Miranda@modemcable235.127-131-66.mc.videotron.ca) 14.46.24 # TheSeven, can we put an assertion on that assumption (e.g. panic if it's not the case)? 14.46.45 # bertrik: that would make sense 14.46.49 # TheSeven: that needs to be checked, but except if you open the same file twice of writing (which is undefined), I think yes 14.47.06 # we could also try to just sequentialize those accesses through locking 14.47.18 # bluebroth3r: just test if a manual still builds? 14.47.47 # pixelma: yes. Should give you much less output on stdout (the log file won't be affected in case you need more information) 14.48.06 # it does some truncation (or to be more precise, it doesn't do reflowing) but that shouldn't hurt. 14.48.24 # pamaury: how are files read/written? 14.48.57 # is that always done through that file's sector buffer? 14.48.58 # I think file.c has a buffer per file 14.49.08 # And that's all 14.49.15 # for reading at least 14.49.30 # will that be bypassed for big accesses that need to read a whole sector? 14.50.09 # hm, even if it is, the current code will already have to deal with the r/w conflict anyway 14.50.58 # so it looks like we basically don't need to care about write accesses, they'll just have to be done in a safe manner, which should already be the case 14.51.33 # bluebroth3r: patch fails (on an updated SVN r26986) 14.51.50 # Looking at the code, it seens read>one sector trash the cache and just read 14.52.20 # are file writes cached? 14.52.34 # (if you only write a few bytes at a time until the sector is full) 14.52.37 # bluebroth3r, pixelma: Any objection to me changing the tagmap environment to "\tabularx{\textwidth}{>{\raggedright\arraybackslash}p{.42\textwidth}X}\toprule\rowcolor{tblhdrbgcolor}" 14.52.48 # or is the whole sector rewritten for each write? 14.52.56 # It means that the second column doesn't end up with space for only a couple of characters 14.53.08 # I'm not sure but I think it is cached until trashed, so it can write a whole sector at once 14.54.00 # AlexP: can't think of any ;) 14.54.00 # pixelma: urgh? Have you used -p1? 14.54.04 # yes 14.54.16 # * JdGordon is stumped 14.54.33 # * bluebroth3r is puzzled 14.54.51 # I've made that patch from an r26986 checkout :o 14.55.01 # how the heck do I incoportate the new skin parser (which dumps a completly different data structure) without having to recode everything at once? 14.55.18 # this patch is turning mammoth and I havnt actually got anything workling yet 14.56.39 # TheSeven: if I read the code correctly, if the write is < one sector, it's just a memcpy if it fits into the sector cache, otherwise, it's write through for all bytes except the tail which is cached 14.57.01 # ok, so that's a clever single-sector cache 14.57.11 # yes 14.57.17 # that would be stupid otherwise 14.57.50 # bluebroth3r: .rej looks like I could apply the two failed hunkjs (#2 and #3) by hand 14.58.01 # hunks too 14.58.11 # New commit by 03alex (r26987): Add multifont to the manual. Closes FS#11294. 14.58.26 # New commit by 03alex (r26988): Adjust the tagmap table environment so that the second column doesn't end up tiny. It can be adjusted further if necessary. 14.58.43 # New commit by 03alex (r26989): Convert the manual to the new theme syntax. As a result, adds the viewport colour tags which closes FS#11372. Correct multifont tag from %F to %Fl 14.58.48 # pixelma: just tried it on mac, patching fails here too. I really don't understand why :( 14.58.49 # TheSeven: it would be a good thing to have an api before starting coding 14.59.40 # bluebroth3r: my guess is because patch is stupid about $ or * or a sequence with these 14.59.47 # r26987 build result: All green 15.00.49 # an uneducated guess though 15.01.25 # r26989 build result: All green 15.01.29 # probably. But if that's the case wouldn't others have hit that issue before and (hopefully) it gotten fixed years ago? 15.01.30 Quit antil33t (Read error: Connection reset by peer) 15.01.36 Join antil33t [0] (~Mudkips@203-184-54-232.callplus.net.nz) 15.01.44 # fortunately it's not a big deal for this patch. 15.01.57 # We appear to be building on all manual changes already 15.02.09 # Given those last three commits of mine were all manual folder only 15.02.17 # AlexP: afaik the build system doesn't filter on directories at all 15.02.33 # New commit by 03Buschel (r26990): Fix FS#11416. Resuming mpc was broken since r26032 due to false assumption of amount of buffered data. 15.02.34 # It used to I think 15.02.36 # AlexP: but we don't build manuals 15.02.54 # But it might not do since the change 15.03.02 # pixelma: Which makes it a bit pointless :) 15.03.05 # yes, the old one did filter. 15.03.46 # it used to but that's already a while ago, IIRC it changed with the new build system which was invented during DevCon 2009 IIRC 15.03.52 # so about a year ago 15.03.53 # pamaury: do you know by chance how many open dirs/files are supported and what the fat cache size is? 15.04.10 # r26990 build result: All green 15.04.17 # It's written in the headers, it depends on mem size 15.04.52 # What happens if you call udelay(0) ? 15.05.28 # 11 open files (file.h) 15.05.55 # 8/12 open dirs (dir_uncached.c) 15.06.44 # fat cache: 0x20 sectors (fat.c) 15.07.23 # bluebroth3r: it's a bit weird to see nothing. I can't tell if your change works or not :\ 15.07.25 # ok, so the sector cache should probably be something like 64 sectors in size 15.07.39 # that's 32/128K, sounds reasonable 15.07.54 # searching 64 entries when looking for a sector also shouldn't hurt too much 15.08.57 # bluebroth3r: I tried a "make clean && make manual" in a build directory that worked before and it was not cleared yet 15.08.59 # pixelma: you should see something. Most output for me is about overfull and underfull boxes 15.09.17 # so I guess it doesn't work 15.09.52 # but I didn't get an error message, haven't tried with your changes in SVN right before though 15.10.25 # strange. I'd expect it to behave identical than on my linux box 15.11.30 # hmm... pressing Ctrl+C to abort the process makes it go on with cleaning and building 15.11.38 # something has hung before? 15.11.45 # TheSeven: http://pastebin.com/X8c0wfpC, does that sum up the wanted operation for the cache ? 15.12.28 # no idea. 15.12.39 Join grawity [0] (grawity@wind.nullroute.eu.org) 15.12.43 # * grawity looks around. 15.12.51 # Where do I post feature requests? Flyspray? 15.13.51 # * TheSeven just writing the very same on pastie :-P 15.13.51 # grawity: no, you can only discuss feature ideas in the forums 15.13.51 # :( 15.13.55 # pixelma: output looks like this for me (only parts of it): http://pastebin.com/89JkGbgX 15.14.10 # * grawity tries to find an apropriate forum for requesting a graphical volume bar. 15.14.21 # I'd have a really nice WPS with that. 15.14.31 # you can already have it 15.14.35 Quit Buschel (Ping timeout: 276 seconds) 15.14.51 # pamaury: i would split the writing thing into "flag a buffer as dirty" and "clean a buffer" 15.15.07 # grawity: AFAIK, haven't tried myself but S_a_i_n_t has I believe ;) 15.15.30 # pixelma: I need something that works in the same way as %pb progress bar - is it already available? 15.15.36 # the fat code will probably want to release buffer handles without cleaning them 15.15.50 # what is cleaning for you ? write back ? 15.15.50 # grawity: yes, I think so 15.15.55 # pamaury: yes 15.16.16 # Yeah, that make sense, leave the write back handling to the cache 15.16.38 # pixelma: I'd really like to commit that change. But if it's not working on cygwin that's a blocker :( 15.16.39 # yes, while keeping the ability to forcible write something 15.16.47 # bluebroth3r: yes, works now but the hang is really weird 15.16.49 # forcibly* 15.16.53 # Ok, agree. 15.17.02 # pixelma: can you reproduce that hang? 15.17.04 # pixelma: What tag is it, then? (I hope it's not %xl/%xd, that would need lotsa RAM.) 15.17.26 # New commit by 03jdgordon (r26991): fix ffwd/rewind on touchscreen targets using regions 15.17.47 # TheSeven: can you edit the pastebin ? I need to leave now, but I'd appreciate if you could write the prototypes in it, so I can begin working or other people can give an opinion 15.18.09 # grawity: there are two ways you can do a graphcal volume display 15.18.25 # I *believe* you have to assign the %pv the parameters you would assign to %pb but as I said I haven't used it myself yet 15.18.31 # either like a progressbar %pv(... same tags as %pb ... ) 15.18.45 # Thanks, I'll try 15.18.48 # or using the %?pv<> conditional which is complicated 15.18.54 # r26991 build result: All green 15.19.03 Quit petur (Quit: *plop*) 15.19.17 # S_a_i_n_t seems to have used "%pv(0,0,122,11,Volumebar.bmp)" 15.19.28 # thats the simple way 15.19.39 # bluebroth3r: I'll try, also without the patch, just the things you already checked in 15.21.09 # pixelma: ok, great 15.21.24 # * bluebroth3r goes building a complete manual round 15.21.42 # New commit by 03jdgordon (r26992): woops, this chaneg too 15.21.48 # JdGordon: The "complicated" way crashes and burns :P 15.21.54 Quit bmbl (Quit: Bye!) 15.22.18 # (if you try to use more than one bar) 15.22.26 # Btw, when is %Vb actually used? I did not notice it ever having any effect... 15.22.56 # it will only work if you dont have a background image 15.23.02 # Ah. 15.23.22 # r26992 build result: All green 15.24.03 # %?pv failed drastically last time I tried it. 15.24.10 # hence the "simple" way. 15.24.41 # I thought the simple way was just a %pv() without being in a conditional. 15.24.48 Quit t0rc (Remote host closed the connection) 15.24.54 # yes, it is. 15.24.59 # (read above) 15.27.17 # S_a_i_n_t: what happens without the bar for +0dB? 15.27.54 # pixelma: It never draws, and its presence messes up drawing the -0dB bar :/ 15.28.09 Join thefirstM [0] (~quassel@cpe-174-098-240-006.triad.res.rr.com) 15.28.22 # grawity: This is partly why we don't have feature requests - 1) It is pointless, devs work on what they want and 2) People request things that already exist and are in the manual 15.28.28 # keeping the conditional "branch"? 15.28.38 # AlexP: Sorry, didn't notice it in the manual :\ 15.28.45 # (And I've read it a few times.) 15.28.46 # pixelma: ...? 15.29.06 # rasher: ping? 15.29.24 # the line as I posted earlier, which I would expect to work, fails in the mannor I described. 15.30.15 Quit Bagder (Ping timeout: 260 seconds) 15.30.19 # pamaury: http://pastebin.com/iRsxt4cu 15.30.32 # S_a_i_n_t: %?pv for example, just replacing the last "bar" definition, not removing the last part completely 15.30.58 # pixelma: Yes, that works as expected. 15.30.59 # I just read it "crashes and burns", so I'm not sure how it fails 15.31.35 # "It never draws, and its presence messes up drawing the -0dB bar :/" 15.31.36 # now I'm confused but will leave it this way 15.32.38 # it just won't draw the +0db Bar, and if you try to, it draws the -0dB bar incorrectly. 15.32.42 # (better? 15.33.44 # Aww :( So I can't have a different background behind the volume bar... 15.33.58 # of course you can 15.34.08 # we're talking about something entirely different 15.34.37 # grawity:^ 15.34.55 # I don't know what you're talking. I just tried %xd(V)%pv(0,0,162,16,vb.bmp) 15.35.02 # grawity: The easiest way to do that is to include the backgroung for the volume bar in the backdrop. 15.35.13 # then you don;t waste any buffer on a seperate image 15.35.20 # Meh. 15.35.33 # What I was trying to do is an ipod-like volume bar 15.35.38 # %xd(V)%pv(0,0,162,16,vb.bmp) <--will not work at all :/ 15.35.46 # (Appears when changing volume, disappears in a second) 15.35.46 # bluebroth3r: seems I can't reproduce anymore, weird 15.36.06 # grawity: Try looking at the tags first. 15.36.16 # you want "%mv" for that. 15.36.19 # I do have that. 15.36.29 # pixelma: does the SA9200 manual build? 15.36.40 # But when I change the volume... the %xd(V) background blinks for a second, then volume bar appears and the image is gone. 15.37.02 # grawity: pastebin the code. 15.37.03 # the platform file uses a file name differing to the target name. I guess that will break 15.37.10 # I suspect you're doing it wrongly. 15.37.15 # bluebroth3r: don't think so and I believe I asked if someone knows if it ever did during DevCon 15.37.24 # I have an Apple_OF theme working very well. 15.37.38 # I'll upload the entire thing in a moment 15.37.40 # TheSeven will testify to that ;) 15.37.40 # bluebroth3r: no-one answered... ;) 15.37.50 # S_a_i_n_t: no, the bars don't come flying in from the side :-P 15.37.58 # grawity: No, please done. Jst pastebin the WPS 15.38.00 # ok, the sa9200 also misses the keymap file. 15.38.10 # so it's definitely broken. 15.38.13 # *s/done/dont/ 15.38.49 # S_a_i_n_t: http://sprunge.us/IgiO 15.39.50 # bluebroth3r: how does a broken manual look with this output, or do I have to try myself? 15.39.59 # Viewport (p) is just: "%al%pc%ac%pp of %pe%ar%pr" 15.40.04 # ? 15.40.10 # S_a_i_n_t: There are two viewports with the same identifier. 15.40.25 # do they overlap? 15.40.44 # S_a_i_n_t: It's allowed by the parser. But it's not the problem. It occurs even with the second p and v viewports removed. 15.41.00 # yes, I know...do they overlap? 15.41.13 # if so, you should just call them in the same viewport 15.41.16 # pixelma: sa9200 manual after renaming the platform file with my changes: http://pastebin.com/N4Rb1QHy 15.41.22 # Hmm. Maybe I could 15.41.31 # yes, you can. 15.41.39 # But anyway, the problem is only with the first one -- below "Conditional Progress/Volume bar". 15.41.41 # I suspect it is trying to draw both at once. 15.42.27 # S_a_i_n_t: Fine: http://sprunge.us/OPXd 15.42.37 # That's what I had at the moment of complaining :/ 15.42.44 # pixelma: for a manual that usually builds you get something like this (excerpt): http://pastebin.com/QHrXiK80 15.43.05 # Please don't get pissy with those trying to help:/ 15.43.09 Join Bagder [0] (~daniel@rockbox/developer/bagder) 15.43.11 # They give up quickly. 15.43.23 # so it's much easier to spot the error as a lot of uninteresting stuff gets filtered away. 15.43.48 # S_a_i_n_t: I'm not... I just think you misunderstood me when I said that the "playlist position" viewports are not the problem I have. 15.43.52 # the solution is not the nicest but it's a quick one :) 15.43.54 # Anyway, sorry. 15.47.26 # the solution is to either draw two viewports in the same place, and display them conditionally (hard-ish), or just encorporate the background for the volume bar in the backdrop. 15.47.36 # +(easy) 15.47.52 # but doesn't work for having an appearing bar 15.48.00 # well, not nicely 15.48.08 # I have a working solution, but mine is different as it shows the progressbar, and the volume only if being changed. 15.48.09 # Well... the backdrop already has a background at that location. 15.48.21 # then, do the first. 15.48.25 # S_a_i_n_t: Yes, that'd do it 15.48.40 # Isn't the first what I'm doing? :( 15.48.43 # two identical viewports, one with the volume-bar, the other with the backdrop. 15.48.57 # show one when %mv is true, the other when it is false 15.49.01 # Hmmm. 15.49.26 # bluebroth3r: does a usual "make manual" not stop on errors now? 15.49.34 # with the patch 15.49.44 # or even without 15.50.24 # S_a_i_n_t: The problem is, it is exactly what I am doing :( 15.50.29 # grawity: you're working one the Nano right? 15.50.33 # Mhm 15.50.36 # do you want me to save you some time? 15.50.37 # * grawity uploaded the thing to http://nullroute.eu.org/~grawity/files/electricbars.zip if you have rockboxsim/ipodnano2g 15.51.15 # * grawity even made sure it isn't running out of memory or something. 15.51.20 Quit flydutch (Quit: /* empty */) 15.51.31 # bluebroth3r: I even got the pdf now but the place where I placed an error is blank 15.52.05 # you don't get a "! " for that line? 15.52.06 # (used a \ButtonSelect in an H10 manual which has no \ButtonSelect) 15.52.35 # I prefer if it stops when compiling for myself, saves me from digging through the log :\ 15.53.39 # I can't find it 15.53.54 # too bad. 15.54.34 # I guess I have to give that issue a more detailed look then :'-( 15.56.23 # I don't want non-stop mode for myself... and there is no ! in the complete log (except in the grep rules at the top), pasted in a text editor and let it search 15.57.06 # well, you escape ^Unde 15.57.42 # which will suppress the "Undefined control sequence" too which probably occurs in my case, IIUC 15.57.47 # afaik every error report starts with a ! as the first character. 15.58.14 # so that should definitely show up. 15.58.43 # haven't seen error reports in non-stop mode 15.58.45 Quit hebz0rl (Ping timeout: 265 seconds) 15.59.00 # I can paste you the log if you want 15.59.15 # would be interesting. I'll try here as well. 16.01.20 Join bmbl [0] (~Miranda@unaffiliated/bmbl) 16.01.26 # in any case, I don't want non-stop mode 16.01.33 # (forced) 16.02.18 # you can always empty LATEXOPTS again. We have nonstopmode since quite a while now. 16.02.37 # though it might be a good idea to use some V=1 method to override that 16.03.05 # I never used it and was never forced to 16.03.26 # it's been in the Makefile :) 16.04.03 # the only problem is (was) that due to some bug nonstopmode wasn't activated for the first LaTeX run if the aux file was missing 16.05.38 # How do you build GCC 4.5 for the arm-eabi toolchain? There were some conversation about that here yesterday. I tried, but I always get the error "checking for library containing strerror... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES." 16.06.59 *** Saving seen data "./dancer.seen" 16.07.46 # using interactive mode in conjunction with filtering would be bad. And IMO building shouldn't fall into any interactive mode. 16.08.18 # bluebroth3r: I really prefer a stop when working for myself... seems that I also understand now why I even got a manual or at least a running build and why I started always cleaning the build dir before because it confused me 16.09.44 Quit rasher (Read error: Connection reset by peer) 16.10.09 # "it" - that the build ran and I got a pdf (only in the "manual" subdir, but there were case where the last copy step failed for me before which is why I started to not care about that) 16.11.01 # pixelma: how about something like http://pastebin.com/yJ0tuy3S then? Just set STOP=1 when running make and you're back to the old behaviour 16.11.10 # bluebroth3r: http://pastebin.com/2jsNpGmL (log) 16.11.46 Join hebz0rl [0] (~hebz0rl@dslb-088-067-195-007.pools.arcor-ip.net) 16.12.49 # bluebroth3r: guess I have to revert the first patch? 16.15.58 # to get back the old (broken) behavious: yes. 16.16.11 # huh? 16.16.33 # oh, giess I misunderstood you :o 16.16.34 # I mean before applying the patch you just posted 16.16.49 # yes, it includes the older patch. 16.17.06 # * JdGordon needs a bit of maths help... 16.17.07 # (sorry, didn't pay attention to that when creating the diff) 16.17.13 # JdGordon: 1 + 1 = 2 :) 16.17.32 # btw. does your already checked in change mean we'll always have a manual even if they are "broken" (and except the uploading or daily scripts are broken)? 16.17.46 # I need to setup a system for the touchscreen buttons where a "position" inside the region is returned (for progressbar/volume bar)... whats the best way to do this so it makes sense? 16.17.57 # using the width/height of the region 16.18.02 Quit bieber (Ping timeout: 252 seconds) 16.18.11 # do I just calculate the percentage position of the touch? 16.18.20 Join bieber [0] (~quassel@162-78.97-97.tampabay.res.rr.com) 16.18.26 # then the user converts that to a usable number 16.18.34 # pixelma: no, if building fails no output file will get generated. However, building won't hang (which I guess could be a problem with nightly builds) 16.19.52 # JdGordon: depends on what exactly you want to tell. Maybe how exact the user hit the middle of the area? Then make center = 100%, and the edges 0% 16.20.15 # Anyone with a c200v2, e200v2, fuze willing to test a patch (updated i2c driver for radio) ? 16.20.37 # or return an x and y value calculated from one of the edges. 16.20.46 # bluebroth3r: right now it is hard coded for use with the progressbar and volume bar... it doesnt need to be precise 16.20.54 # bluebroth3r: but I got an output file now (with the first of the other patches though), not only in the manual subdir you can see that the copying didn't fail in the log 16.21.16 # an egde offset would certainly be simpler :) 16.21.19 # I'll do that 16.21.21 # thanks 16.22.17 # pixelma: hmm. Right, that would then be an incomplete file (i.e. only the manual part up to the error) 16.22.30 # * bluebroth3r should get more coffee 16.22.34 # no 16.22.49 # not? 16.23.03 # just the cell in the button table with the wrong button was empty 16.23.45 # ok, that surprises me. Wouldn't be too bad of a behaviour though, at least for nightly builds 16.24.31 # not sure, then you'll probably get a bunch of errors before someone notices :Y 16.24.37 # btw, in case the manuals disappear I've uploaded a set of current ones to http://www.alice-dsl.net/dominik.riebeling/rockbox/ 16.24.39 Join rasher [0] (~rasher@rockbox/developer/rasher) 16.24.43 # or :| 16.25.34 # and less incentive to get the manuals into the build system ;) 16.26.30 # bluebroth3r: bah, no a single offset isnt enough, I need the full width/height value also somehow 16.26.45 # well, catching the errors should work though. We then only need some kind of build table 16.27.11 # One more question. What does the "0%|" thing mean in this line: %X(backdrop.bmp)0%|0%| 16.27.22 # I find it in some WPSes... 16.27.54 # looks like a wrong conversion because someone used it wrong in the old syntax 16.28.24 Join halmi_ [0] (~netbook@80-123-34-41.adsl.highway.telekom.at) 16.29.13 # the 0%|0%| shouldn't be there 16.30.05 # * grawity removes 16.30.29 Quit halmi (Ping timeout: 240 seconds) 16.30.35 # a backdrop doesn't need setting the coordinates, some people used %X|backdrop.bmp|0|0| before for some reason. The automatic conversion "thought" | was meant to be displayed "literally" there which needs escaping with % 16.36.12 Join funman [0] (~fun@rockbox/developer/funman) 16.37.13 # pixelma: Funny thing is, it passes checkwps like that. 16.37.24 # its the ElectricBarsOfColour thems. 16.37.38 # (And Cabbie v3.) 16.38.17 # it's not wrong I guess, not sure you could find a 0|0| on screen somewhere 16.38.31 # pixelma: it is wrong. 16.38.36 # it fails on device now. 16.38.40 # it wont be displayed because the current(old) parser eats the whole line 16.38.48 # it didn't *used* to be wrong though. 16.39.10 # everything past the | after the bitmap image gets ignored. 16.39.13 # or used to. 16.39.55 # TheSeven: isn't aligning stack buffers simpler? 16.40.11 # But now it manages to pass checkwps, yet fail on device...how this works I have no idea. 16.40.22 # S_a_i_n_t: It works on the device too. 16.40.34 # funman: this means we have to reserve like 4K for sector buffers on several threads' stacks 16.40.54 # grawity: Perhaps a recent thing. 16.41.11 # It failed on device as little as a week ago (I tested it on two targets) 16.41.36 # topik brought it to my attention. 16.41.49 # TheSeven: ah this explains the stkov on nano2g 16.41.59 # S_a_i_n_t: Huh. I used Cabbiev3 for several months, with that line. 16.42.19 # bertrik: udelay(0) should sleep for ~17 seconds 16.42.28 # grawity: with the *old* syntax? 16.42.37 # ah :) 16.42.38 # must have...new syntax isn't that old. 16.42.45 # S_a_i_n_t: Oh, now that you mentioned it... *facepalm* 16.42.53 # hehehe 16.43.13 # funman: yes, I want to finally get rid of the root cause for them 16.43.15 # It *should* fail the new syntax. 16.43.35 # yet it passes checkwps, not a big deal, but misleading. 16.44.22 # bluebroth3r: I'm confused now, I thought I applied your newer patch but the output looks like the "old" one 16.44.39 # Meh, I give up. Whatever I try to put behind a progress or volume bar doesn't get displayed, even though half of that bar is 'empty'. ...I guess I'll make it something like original appleware screen. 16.44.57 # iiuc fat/sd accesses are already protected by a mutex 16.45.19 # i'm not sure if you can access 2 drives at the same time 16.48.10 Join panni_ [0] (hannes@ip-95-222-52-93.unitymediagroup.de) 16.49.47 # bluebroth3r: ah, the "STOP=1" will give me the "old" output? Thought it would also cut the warnings but just not go on when an error occurs 16.53.46 Quit Highlander (Quit: Quitte) 16.55.08 Join Jerom [0] (~heidi@79.132.53.242) 16.56.57 # pixelma: yes, that was the idea. Maybe naming it INTERACTIVE would be more clear. Changing the filtering could be done as well. 16.57.07 Quit thefirstM (Remote host closed the connection) 16.57.41 # just move the LATEXFILTER in LaTeX.Rules 17.03.39 # anyone want to test fms touchscreen skin support patch? 17.08.39 Quit stoffel (Ping timeout: 252 seconds) 17.08.44 # bluebroth3r: did you see http://forums.rockbox.org/index.php?topic=25071.msg168332#msg168332 and following by the way? 17.10.41 # and... applying the filter options to the STOP=1 case is weird: it stops but you don't see why 17.11.03 Join greg987 [0] (www-data@giant.haxx.se) 17.11.31 Quit greg987 (Client Quit) 17.11.32 # for some reason it still supresses errors in my case 17.11.59 # pamaury: http://pastebin.com/9hrrijcx 17.16.34 # bertrik: you have an idea on the fuzev2 problems with µSD ? 17.16.50 # it took me several boots to see it happen on my fuzev2 17.18.33 # bluebroth3r: error messages do not start with a ! here. In my example running non-stop mode without the filter gives me "./plugins/pegbox.tex:102: Undefined control sequence. \n \ButtonSelect" 3 times in a row 17.18.40 # no, but didn't you mention something was a bit out of spec in the sd driver? maybe increasing the Fcpu pushed the timing over the margin 17.19.30 # bertrik: i'm not sure if it's out of spec but it definitely works like it is, the same thing is used on AMSv1 17.19.42 # OR maybe the special case for the sdram / PCLK for the fuzev2 has something to do with it (although this was tested) 17.19.53 # bit6 of CGU_PERI ? 17.20.20 # perhaps adding some logf in fat code would help 17.20.58 Join greg987 [0] (~greg@g229229058.adsl.alicedsl.de) 17.21.16 # How do I do the (c) notice for a new file which I'm copuing code out of a old one for? 17.21.50 # bertrik: also I want to make sure the recent changes to SD are 100% working 17.22.43 # alright, there is something fishy in text_viewer preferences 17.22.49 # I think it is mostly origionally my code, but I dunno... 17.23.05 # funman, OK. I have no problem with you reverting the 248 MHz change, by the way :) 17.23.07 # making tv_set_preferences() return immediately stop crashes (i can't see anything on screen however) 17.23.14 # ok nice 17.23.34 # hopefully we will get an eureka soon on this :) 17.26.10 Join GeekShadow [0] (~Antoine@reactos/tester/GeekShadow) 17.27.45 # funman, I have the strong suspicion that we can't really make 240 MHz out of 384 MHz with the 5/8 pre-divider. I think the pre-divider just skips cycles, so the cycles that it doesn't skip will be at 384 MHz (i.e. too fast) 17.28.04 # iirc it worked on AMSv1 17.28.54 # wouldn't this be a problem if we set pre-divider to 5/8 and postdiv to 1/2? 17.29.15 # the cycles would be below 240MHz 17.30.56 # Hey, I'm running my ipod without battery (since it didn't hold any charge and also seemed to be bloated somehow). Now I encouter continuous resets/crashes at pretty precisely the same time after boot-up (about 30s into the song). I wouldn't like to risk buying a new replacement battery that then might just bloat up again (I have it plugged in all the time, anyways). Anybody some ideas how to fix these crashes? 17.31.22 # yes that would work, but wouldn't Fcpu be rather slow then (120 MHz)? 17.31.23 # http://pastebin.com/CJxMZs7j 17.31.41 # do we have a wiki page for how the touchscreen is supported? 17.31.50 # TheSeven: what is the consistent flag ? 17.31.56 # bertrik: yes it would be slow, i just meant that scheme as experiment, not something to be committed 17.32.03 # ok 17.32.30 # pamaury: that indicates that the state of the sector buffer is currently consistent enough to be written back if needed 17.32.52 # this is only needed for that clean_all thing which we might as well just drop 17.33.33 # and sectorcache_wait_block ? 17.33.59 # that will block the current thread until some buffer was released or flagged consistent 17.34.16 # (should actually be static) 17.34.28 Quit grawity (Quit: Leaving.) 17.34.38 # ok 17.34.54 Quit DerPapst1 (Read error: Connection timed out) 17.35.58 # i'm still not sure how to handle hotplug though 17.36.02 Join DerPapst [0] (~Alexander@p4FE8F654.dip.t-dialin.net) 17.36.44 # can we assume that all locks to that drive's sector buffers will have been removed before the remounting happens? 17.36.51 # That's the problem with caching, if the user remove the card, we are dead :) 17.37.27 # i don't care about the user deliberately unplugging the card 17.37.37 # but we need to invalidate everything when he plugs a new card 17.37.43 # I would say no, you can't assume that 17.37.55 # Do you plan to use a timer to write back after x seconds ? 17.38.11 # i'm not sure about that yet 17.38.18 # how does the fat cache currently handle this? 17.39.59 # it does nothing about it I think 17.41.13 # so if the fat gets written to, that won't be written to disk until it runs out of cache space or the player is shut down? 17.41.21 # (how does it actually intercept the shutdown?) 17.41.58 # or is the fat cache write-thru? 17.42.56 # No, the fat is written back when a file a created/closed(and modified)/removed/renamed 17.43.04 # So it's reasonably safe 17.43.39 # ok, so cleaning is triggered actively 17.43.55 # we could do the same for the sector cache 17.44.21 # pixelma: gnah, then this filtering obviously won't work :( What LaTeX distribution are you using? 17.44.41 # as for the ligature issue: it doesn't appear anymore in recent manuals because of the switch to T1 fontenc. 17.45.25 # probably an old one... how to find out 17.45.44 # aha, about the other answer 17.47.57 # bluebroth3r: pdfeTeX 3.141592-1.21a-2.2 (Web2C 7.5.4) <- do you mean that one? 17.48.50 # well, I was rather referring if you are using MikTeX, TexLive or something else. Cygwin packages I guess? 17.49.19 # the latter, tetex and tetex-devel I believe it was 17.49.33 # but my system reports pdfTeX using libpoppler 3.141592-1.40.3-2.2 (Web2C 7.5.6) so it's definitely newer 17.50.01 # tetex is outdated and no longer maintained. AFAIK all linux distributions now use TeXlive 17.50.12 # I know 17.50.25 # anyway, this leaves us with the problem that we can't do this filtering that way. Too bad :( 17.52.00 # might work by adding "|.+\:[0-9]+:" before the closing bracket for LATEXFILTER 17.52.12 # * pixelma looks around for someone running the newer cygwin 1.7 17.56.27 Quit greg987 () 17.56.49 Join Antibuddha [0] (~chatzilla@c-71-59-19-167.hsd1.ga.comcast.net) 17.56.56 # how do i play videos with rockbox on ipod 5g? 17.57.08 # i need mpegplayer? 17.58.08 # Antibuddha: check the manual, mpegplayer is explained 17.58.19 # ok 17.58.23 # im setting up an ipod for my mom right now 17.58.33 # would it be better for video quality to dualboot? 17.58.55 # pamaury: http://pastebin.com/LshWrjr6 17.59.10 # see for yourself 18.00.02 # pamaury: if we run out of sector buffers, should we 1) panic, 2) return an error or 3) block until one gets freed? 18.00.42 # i dont have time funman 18.00.46 # Antibuddha: on the Ipod Video it's still better to use the original firmware for videos I believe. Apple can use a special chip for it which Rockbox can't 18.00.55 # have to leave home to take mom to airport in 30 min 18.01.00 Quit bucko (Ping timeout: 258 seconds) 18.01.01 # I would say block, or even better, block with an optional timeout after which is fails 18.01.01 # ok 18.01.49 # TheSeven: what is sectorcache_replace_idx ? 18.02.03 # a rotating index where to start to look for free buffers 18.02.33 # what is the difference between valid and free ? 18.03.28 # invalid = garbage, free = contains valid and up-to-date data for that sector, but isn't expected to be used again and should thus be re-used preferably before killing other buffers 18.04.24 # Ok 18.04.31 # i found text_viewer problem: char[XXX] = (struct font *) 18.04.40 # You should comment each flag to make it clear what do they them 18.04.43 # dunno why gcc didn't warn 18.05.35 # argh no it's correct >< i can't read 18.07.00 *** Saving seen data "./dancer.seen" 18.11.39 Join t0rc [0] (~t0rc@unaffiliated/t0rc/x-5233201) 18.14.55 Join fml [0] (www-data@giant.haxx.se) 18.16.50 # AlexP: hello. I see some typos in the recent manual commits, but don't have svn access to fix them. One is in advanced_topics/main.tex ("declerations"). The other is in advanced_topics/viewports/colour-vp-syntax.tex: "and 2-9 are additional are skin loaded..." 18.17.13 # Thanks, I'll fix now 18.17.37 # Hmm, static variables in a function for no special reason? 18.17.51 # * amiconn is trying to solve the weird lines problem in PF 18.18.23 # AlexP: other variants of the VP syntax have the same typos. 18.19.28 # pamaury: http://pastebin.com/5vjMFdrf 18.19.47 # fml: Incidentally, I copy/pasted these from the wiki :) 18.20.55 # AlexP: also, in appendix/wps_tags.tex, the text \config{\%Vi(`label',\dots)} should not use fancy apostrophes since it's code. 18.21.13 # AlexP: yes, copy-paste, I guessed it :-) 18.21.18 # fml: Either way is wrong 18.21.27 # '' doesn't just do ' either 18.22.25 # AlexP: I don't understand. Before "label" is a fancy apostr. 18.23.35 Quit fml (Quit: CGI:IRC) 18.23.44 # TheSeven: shouldn't an entry with 0 locks be free ? 18.23.49 # New commit by 03alex (r26993): Fix typos/c&p errors. 18.24.11 # 0 locks, free = false => can be reclaimed, but is likely to be re-used 18.24.26 # 0 locks, free = true => should be reclaimed first, not likely to be re-used 18.24.40 # and how do you switch between these two states ? 18.24.59 # see the keepincache argument to sectorcache_unlock 18.25.16 # maybe also in writethrough/readthrough 18.25.30 # ok 18.25.33 # r26993 build result: All green 18.27.19 # http://pastebin.com/RMAb7Ejf 18.27.43 # New commit by 03alex (r26994): Use normal apostrophes for code. Thanks to fml for pointing out (also for previoys commit). 18.29.04 # r26994 build result: All green 18.29.17 # bluebroth3r: the "firmware" in the mentioned headline still has the "fi" ligature 18.29.38 # TheSeven: what did you change ? 18.29.44 # added some comments 18.29.49 # bluebroth3r: in a daily pdf (June 17th) off rockbox.org 18.29.51 # just saw 18.31.42 Quit t0rc (Remote host closed the connection) 18.32.27 Quit hebz0rl (Quit: Ex-Chat) 18.32.47 # you want to remove ligatures? 18.33.02 # New commit by 03amiconn (r26995): Make unnecessarily static local variables non-static. It's more efficient, and it also fixes the weird lines with EABI on ARM7TDMI, although it ... 18.33.40 # pixelma: really? Even if you copy the text with Adobe Reader? I can't reproduce this with the svn manuals I did earlier today. 18.34.17 Quit BHSPitMini (Read error: Connection reset by peer) 18.34.30 # r26995 build result: All green 18.34.32 # * bluebroth3r wonders what TeX distribution the build server uses 18.35.07 # yes, well with the pdf plugin in firefox (which I think is acrobat reader, as I haven't installed any other PDF readers) 18.35.11 Join hebz0rl [0] (~hebz0rl@dslb-088-067-195-007.pools.arcor-ip.net) 18.35.47 # * bluebroth3r is puzzled (again!) 18.36.06 # amiconn, weird ... 18.36.14 # yes 18.36.14 Join BHSPitMini [0] (~BHSPitMon@ppp-70-243-200-93.dsl.rcsntx.swbell.net) 18.36.16 # funman: For things like "fi" in the word "firmware", yes - they should of course be separate letters 18.36.20 # bluebroth3r: same with my own PDFs 18.36.36 # The lines themselves are most likely a gcc bug, which is just avoided now 18.36.38 # hmm. Maybe caused by an older LaTeX installation? 18.36.50 # wouldn't surprise me 18.36.52 # i thought ligatures were cool 18.37.18 # Having simple local vars static is weird though, except for special reasons (which don't apply here) 18.37.30 Quit Antibuddha (Quit: ChatZilla 0.9.86 [Firefox 3.6.3/20100401080539]) 18.38.03 # Bagder: can you figure which LaTeX version the build server uses? 18.38.19 # funman: Not when you try to search for words :) 18.39.07 # LaTeX is supposed to use Ligatures. However, it should embed the text without ligatures for searching / copying. 18.39.40 Join pamaury_ [0] (~quassel@p5DDEE734.dip.t-dialin.net) 18.40.23 # I haven't tried this personally incidently 18.43.31 # text_viewer data aborts are linked to footer/header 18.43.46 Quit pamaury (Ping timeout: 265 seconds) 18.44.07 Nick pamaury_ is now known as pamaury (~quassel@p5DDEE734.dip.t-dialin.net) 18.44.21 Quit pamaury (Changing host) 18.44.22 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 18.44.40 # pamaury: what are you doing right now? who of us should continue fleshing this out? 18.47.07 # right now, whatching a film :) If you are boring, put in in a pastebin and I'll continue it (well I'll try). We don't have a deadline anyway, so it's not for tonight :) 18.47.13 # *bored 18.47.36 Join flydutch [0] (~flydutch@host110-154-dynamic.14-87-r.retail.telecomitalia.it) 18.47.39 # ok, then i'll continue to work on this 18.50.41 # "If you are boring" :P 18.51.40 # S_a_i_n_t: that's why I I rectified ;) 18.51.54 # hrrrm 18.52.06 # Somehow current rockbox is very unstable 18.52.29 # In what way? 18.53.02 # I haven't noticed anything untoward with 26990...yet 18.53.07 # Data aborts, bootloader unable to find rockbox.ipod, ... 18.53.16 # That's on ipod color 18.54.07 # bugger, that was actually a typo "r26980" 18.54.18 # I'll build latest and see what I find. 18.56.09 # Database commit not working 'live' even though dircache is enabled, scan running again and again... 18.57.46 # database always had problem no ? 18.57.51 # That's not new 18.57.53 # Parhaps what TheSeven and pamaury have been working on has had an unexpected effect? 18.58.03 # pamaury: It used to work a while ago 18.58.14 # S_a_i_n_t: that's only being planned, nothing committed yet 18.58.52 # (a while == a few months; I don't use the database most of the time so I won't notice bugs quickly) 18.58.58 Join stoffel [0] (~quassel@p57B4C717.dip.t-dialin.net) 18.59.00 # Ah, right. And your earlier commits were nano2g specific...yes? 19.00.00 # I didn't notice any new database bug recently 19.00.28 # And I use it (only for basic things though) 19.02.53 Join MethoS- [0] (~clemens@134.102.106.250) 19.05.35 # amiconn: if you look at the log for tagcache.c, there has been no real change for more than 9 months, only cosmetics and external fixes 19.05.44 # S_a_i_n_t: those commits just can't have broken something... only preprocessor stuff and higher alignment values for some arrays, can't hurt 19.06.12 Join anewuser [0] (anewuser@unaffiliated/anewuser) 19.06.35 # pamaury: Since it's not *only* the database, I wouldn't even expect the problem there. It must be something more fundamental 19.09.04 Quit guymann (Quit: brb) 19.09.06 # amiconn, eabi changes maybe? Also gevaerts made some changes to prevent contention between threads wanting disk access, maybe this had some influence? 19.19.14 # TheSeven: re r26985, I think PROC_NEEDS_CACHEALIGN is not correct 19.19.28 # what exactly does this do? 19.19.41 # it's only needed for dual core where cache alignement is needed, not just desired for performance 19.20.06 # hm, there are CACHEALIGN_ATTRs on some things that need to be aligned on nano2g, mostly DMA stuff 19.21.48 # see r25339 log 19.22.28 # this isn't only storage stuff, also PCM and the like 19.22.39 # http://www.rockbox.org/irc/log-20100326#00:21:22 19.22.49 # yeah i know but i had talked about thsi with amiconn 19.22.56 # bluebroth3r: adding the things you mentioned to the filter rule lets the error appear but in non-stop mode it's still not easy to find or needs some getting used to (the only thing that does not start with Underfull or Overfull) 19.23.41 # and I get some font warnings 19.24.13 # TheSeven: hm no it was only about the STORAGE macros 19.24.58 # TheSeven: DMA alignement isn't related to cache alignement, is it ? 19.26.28 # which things use CACHEALIGN_* on nano2g? grep target/arm shows nothing 19.28.04 Join CaptainKwel [0] (~jason@207-237-113-115.c3-0.nyr-ubr1.nyr.ny.cable.rcn.com) 19.30.45 # funman: sorry, someone called me on the phone 19.30.57 # aha, so you were the one who broke storage alignment on nano2g by misspelling that define? :D 19.31.06 # probably O:-) 19.31.15 # i already wondered how this could have slipped in and though I did it myself :P 19.32.13 # thought* 19.32.27 Quit stoffel (Ping timeout: 264 seconds) 19.35.05 # New commit by 03theseven (r26996): Remove PROC_NEEDS_CACHEALIGN for Nano2G again, it's only needed for PP 19.36.02 # the D2 has 2 different cores, it would be nice if we can use the 2nd one 19.36.28 # r26996 build result: All green 19.36.45 Quit Bagder (Quit: connection reset by beer) 19.40.40 Quit funman (Quit: free(random());) 19.40.47 Join Bagder [0] (~daniel@rockbox/developer/bagder) 19.41.14 Quit DerPapst (Read error: Connection reset by peer) 19.45.50 Join DerPapst [0] (~Alexander@p4FE8F654.dip.t-dialin.net) 19.46.17 Join jannef [0] (~jan@95-88-18-243-dynip.superkabel.de) 19.47.14 # hi everybody, are there any news about the new v2 fuzes which refuse to installed rockbox-modified firmware files? 19.49.14 Join ubuntu-nathan [0] (ubuntu-nat@187.89.43.61) 19.49.24 # Hi all! 19.49.29 # * ubuntu-nathan is back 19.49.57 # There is any RockBox developer online? 19.50.57 # probably ~100 of them. 19.51.54 # lol 19.52.25 # I want to know where I can get the sources of a very simple(extremelly) simple bootloader for iPod Video 19.52.33 # I don't want the RockBox one 19.52.57 # there might also be ipod bootloaders from ipodlinux. 19.53.04 # because that is so much integrated with RB, then I want something that is only the boot loader 19.53.11 # hmm 19.53.32 # TheSeven: Have a link to their repository? 19.53.40 # nope 19.53.46 # :| 19.53.47 # what exactly are you planning to do? 19.56.01 Join guymann [0] (~charlie@69.0.83.229) 19.58.50 # I've already developed a OS for x86 and for Integrator-CP(ARM) 19.59.01 # but now I want to dive into the iPod world 19.59.01 # :) 20.01.05 Quit hebz0rl (Ping timeout: 245 seconds) 20.01.39 Join saratoga [0] (463f90ed@gateway/web/freenode/ip.70.63.144.237) 20.01.47 # * TheSeven would suggest starting with code *loaded* by the bootloader then 20.05.28 Join stoffel [0] (~quassel@p57B4C717.dip.t-dialin.net) 20.06.57 # TheSenven 20.07.01 *** Saving seen data "./dancer.seen" 20.07.03 # TheSeven* 20.07.21 # what you're saying is that is better to forget the boot loader for a minute 20.07.22 Quit halmi_ (Quit: halmi_) 20.07.30 # create a Hello, World OS 20.07.36 # basically yes 20.07.45 # and use some boot loader to load it 20.07.49 # hmmm 20.07.50 # ok 20.07.59 Quit stoffel (Remote host closed the connection) 20.08.04 # but, did you have any suggestion of docs for me? 20.08.08 # to start 20.08.25 # that way you don't need to care about apple's firmware partition and can just put your code as a regular file on the HDD 20.08.40 # ok 20.08.45 # but 20.08.49 # the best docs on that hardware are probably the rockbox and ipodlinux code 20.08.52 # did you have any docs for me, or a starting point? 20.09.01 # hmm 20.09.09 # I have RB sources here 20.09.27 # where is the "main loaded file" source? 20.09.37 # ubuntu-nathan: it sounds like what you actually want to do is work on a rockbox plugin not a bootloader? 20.09.54 # since a bootloader is mostly device drivers and not an application 20.10.01 # I want to build an iPod OS 20.10.09 # because I have a good base on this 20.10.14 # thats probably unrealistic 20.10.17 # New commit by 03mc2739 (r26997): Revert r26350 - fixes FS#11421 20.10.36 # I've already done an OS for x86(my first one), and one for Integrator-CP(ARM) 20.10.42 # Now I want to go mobile ;) 20.11.36 # I'd suggest looking at the rockbox bootloader source, if you want to dig into the rockbox driver architecture 20.11.41 # well all the drivers are in the bootloader, knock yourself out 20.11.42 # r26997 build result: All green 20.11.48 # ok 20.11.50 # it shares the drivers with the main os 20.11.58 # ok 20.12.02 # I'm on it now 20.12.02 # :) 20.12.27 # pamaury: what should we do if somebody tries to WriteThrough a sector that has an exclusive cache handle? 20.12.46 # kill him ? 20.13.41 Quit Barahir_ (Read error: Connection reset by peer) 20.13.43 # TheSeven: panic 20.13.59 Quit leavittx (Read error: Connection reset by peer) 20.14.01 # we could also just return an error code 20.14.15 # That will hide the problem no ? 20.14.23 Join petur [0] (~petur@rockbox/developer/petur) 20.14.31 # oh! 20.14.37 # I got a better idea! 20.14.40 # :D 20.15.07 # TheSeven: when such a situation could arise ? 20.15.22 # it shouldn't, afaics 20.16.14 # Such a situation in unsafe. It means someone has a dirty buffer for a sector and someone is trying to write it. this is a major programming bug imo 20.16.29 # not neccessarily dirty 20.17.17 # Yes but it will at some point, otherwise, exclusive access is useless 20.17.44 # exclusive access might also be used just to lock out writes 20.17.59 # (to make sure the sector buffer stays consistent across yields) 20.18.43 # or should we say in general that write accesses *must* use exclusive accesses, so that they'll fail if someone else has a handle on it? 20.19.11 # I'm going to do a launcher! 20.19.18 # like those ones for Palm OS 20.19.28 # but now I will do one for RockBox 20.19.33 # :) 20.19.33 # To me, a write should 1) either be done though writethrough 2) either be done with exclusive access, so yes 20.20.21 # that implies that we need to panic if writethrough hits open handles, even if they're non-exclusive read-only 20.20.41 # ok, I'm out 20.21.00 # I'm going to watch the Brazils game(since I'm brazilian) 20.21.03 # Yes, if someone has a handle that has not been release yet, that's a same programming error no ? 20.21.04 # :) 20.21.04 # bye guys 20.36.18 Join M3DLG [0] (~M3DLG@bb-87-81-252-83.ukonline.co.uk) 20.40.10 Join will__ [0] (~chatzilla@76.250.191.129) 20.41.06 # How much work would it take to make the text viewer display rotated 90 degrees? 20.41.37 # will__: that depends on several things 20.41.51 # if your lcd is square and the driver supports rotating, it should be rather easy 20.41.59 # rectangle 20.42.09 # sansa e200v1 20.42.11 # but i doubt that you'd want to do that if your display would be square 20.42.24 # indeed :) 20.51.33 Quit will__ (Quit: ChatZilla 0.9.86 [Firefox 3.6.3/20100401080539]) 20.56.38 Quit flydutch (Quit: /* empty */) 21.00.47 Join katg [0] (~quassel@cpc1-rdng15-0-0-cust791.winn.cable.ntl.com) 21.04.37 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 21.12.07 Quit bieber (Ping timeout: 276 seconds) 21.12.22 Join bieber [0] (~quassel@162-78.97-97.tampabay.res.rr.com) 21.17.22 Quit Xerion (Ping timeout: 240 seconds) 21.20.15 Quit Viaken (Ping timeout: 245 seconds) 21.20.31 Quit saratoga (Quit: Page closed) 21.20.50 Join Viaken [0] (~david@li16-211.members.linode.com) 21.21.35 Quit sharp (Read error: Operation timed out) 21.21.52 Join sharp [0] (~sharp@sauropod.org) 21.22.02 Join domonoky [0] (~Domonoky@rockbox/developer/domonoky) 21.22.20 Nick sharp is now known as Guest53364 (~sharp@sauropod.org) 21.25.20 Quit Topy44 (Ping timeout: 260 seconds) 21.32.47 # do we accept ignoring storage function return codes? 21.33.11 Join Topy44 [0] (~topy@my.fastsh.it) 21.34.37 # It depends on how many lines you want to rewrite :) 21.37.28 # wow... there's a pretty nasty bug in recording: auto-split on 2GB no longer works O_o 21.39.51 # pamaury: tested clip+ for battery draining after shutdown from: rockbox, OF, charging in OF then shutdown. I haven't noticed battery draining. To time I assume we had only impression about that or it changes between versions. Tested with r26959, bootloader r26730. Now testing shutdown from rockbox after charging in rockbox. Is it possible it depends on which version of bootloader we are using? Which one you used? 21.40.36 # can I generally panic if storage_write_sectors returns a nonzero RC? 21.42.10 # pixelma: you could also remove the underfull / overfull warnings from the output. I'm not sure if it's better to filter them out or not 21.42.18 # It might be because of a panic. I basically get a panic every minute when working on usb so perhaps there was a panic but the screen stayed black so I thought it was off but it wasn't 21.42.43 # TheSeven: that seems harsh. It can easily do that on hotswap systems if you unplug at the right moment I think 21.43.09 # TheSeven: most of the code should check for the return values, doing a panic on that is a bit violent 21.43.26 # I've seen quite some code that doesn't 21.43.29 # bluebroth3r: Do they ever mean anything useful? 21.43.57 # and what should I do if i need to write back a dirty sector because I need buffer space, and get an I/O error? 21.45.46 # hum, no easy answer... 21.46.11 # should I make the cache allocation fail? that will make an arbitrary read fail... 21.46.42 # panicing seems to be the only option 21.46.50 # Anyway, at this point it's too late, that would fail an unrelated operation 21.47.06 # On the other end, there is this hotswap problem... 21.47.09 # *hands 21.47.40 # pamaury: It's possible so I'm leaving this. It was only impression :) 21.48.35 # anyway, if such a thing happens, something was corrupted for sure 21.49.05 # TheSeven: anyway, most of code will do explicit cleaning/flushing, so the error will be catchable 21.51.11 Quit katg (Remote host closed the connection) 21.51.20 Quit mitk (Quit: Leaving) 21.51.27 # And in this precise case, well, you can just panic for now 21.54.25 # AlexP: of course they do! 21.54.49 # the thing is that if you want to make proper typesetting you're definitely interested in the overfull / underfull warnings. 21.55.03 # Mmmm, but for us? 21.55.05 # however, for something like our manual they could get ignored in almost all cases. 21.55.11 # aha :) 21.55.43 # it might get interesting if the values get too large, especially for overfull boxes (as this means it prints to the margings, and even outside the margins if necessary) 21.57.00 # no-one notices if there are just too many and 99% of it is ok 21.57.15 # I never pay any attention to them at all 21.57.20 # There are just too many 22.07.03 *** Saving seen data "./dancer.seen" 22.11.22 # hm, why does passing a null pointer to storage_read_sectors silently succeed? 22.14.07 # well, given the fact that even after removing all other output there is still a load of warnings I wouldn't mind removing them too. 22.16.36 Join mitk [0] (~mitk@chello089078013092.chello.pl) 22.19.43 Quit Jerom (Read error: Connection reset by peer) 22.22.54 Quit CaptainKwel (Quit: Ex-Chat) 22.24.17 Quit ubuntu-nathan () 22.24.29 Quit stripwax (Quit: http://miranda-im.org) 22.49.04 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 22.50.36 # pamaury: do we want to keep the fat cache (but probably smaller), or get rid of it? 22.50.58 # i just spotted an advantage of it: it only needs to mirror a single fat 22.51.04 Join kramer3d_ [0] (~kramer@unaffiliated/kramer3d) 22.51.43 # reducing the fat cache size to like 8 sectors and stacking it on top of the sector cache seems to be the best solution 22.52.18 # hmm I tested recording auto-split with the latest build and found it not splitting. To try stuff I did svn up, changed the max filesize to 2MB and that works fine. Wtf? 22.52.46 # TheSeven: I don't see why this an advantage ? 22.52.59 # it only needs half the memory if there are 2 fats :-) 22.54.02 # i don't get it 22.54.09 # Ah yes, ok 22.54.14 # I'm a bit slow :) 22.56.43 # I think we should get rid of it 22.57.08 Join Barahir [0] (~jonathan@frnk-590fcabd.pool.mediaWays.net) 22.58.44 # woah, it even seems to work 22.58.55 # but something is slow as hell 23.04.25 # mc2739, thanks for testing! 23.06.41 # pamaury: oh, that one in write_long_name is really nasty 23.06.54 Quit mitk (Quit: Leaving) 23.09.42 Quit M3DLG (Ping timeout: 260 seconds) 23.09.50 # why ? 23.10.31 # because that buffer is used with fat_readwrite 23.12.11 # i 23.12.30 # i'll need to invent something that gets me a cache handle to a sector of a file 23.15.49 # Or you need to be able to use a sector buffer just as a sector buffer, that's is as storage but not necessarily at a precise sector 23.16.35 Quit jannef (Remote host closed the connection) 23.18.03 # but that means losing the cache 23.18.47 # actually i only need to make that fat_readwrite thing return me a sector number :-) 23.21.30 # No, just be able to use one entry of the cache as a scratch buffer, something unrelated to a precise sector of the disk. It does not prevent caching because caching will already be done indirectly by fat_readwrite 23.22.01 Quit BHSPitMini (Ping timeout: 264 seconds) 23.39.18 Quit petur (Quit: Zzzz) 23.41.04 Join BHSPitMini [0] (~BHSPitMon@adsl-70-243-200-93.dsl.rcsntx.swbell.net) 23.41.54 Quit bmbl (Quit: Bye!) 23.48.45 Quit fdinel (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 23.49.10 Quit TheSeven (Ping timeout: 272 seconds) 23.49.34 # just added a bunch more music to my ipod, booted into rockbox, and decided to watch the Debug -> Database screen. 117% complete? -494731232/-444391366 B used ? 23.52.14 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 23.52.32 Quit BHSPitMini (Ping timeout: 240 seconds) 23.52.54 # hrm , and a massive amount of duplicate entries in the db 23.53.49 # That's probably one of the know-bug-that-no-database-dev-managed-to-get 23.53.50 # New commit by 03funman (r26998): text_viewer: cleanup & bugfix ... 23.54.46 # it seems to have added each *track* as a separate entry in the *albums* tag in the database, somehow. e.g. an album with 5 tracks, has the album name listed 5 times in db. 23.54.54 # maybe that's an unrelated bug? 23.55.02 Join funman [0] (~fun@rockbox/developer/funman) 23.55.12 # [selecting each such entry shows just one track] 23.55.32 # r26998 build result: All green 23.58.43 # i'll just try (re)initializing the db. looks like the update freaked out.