Click in the nick column to highlight everything a person has said.
The icon identifies that the person is a core developer (has commit access).

Notice: Only Gecko based browsers prior to FF4 support the multipart/mixed "server push" method used by this log reader to auto-update. Since you do not appear to use such a browser, this page will simply show the current log, and not automatically update.

#rockbox log for 2010-01-21

is any iPod savvy dev able to tell me what the startup option "hard reset (menu+select) then select+next" does? it draw info on boot which is too small a font for me to read, and displayed too quickly for me to read even if it wasn't. It doesn't seem to do anything (that I've noticed anyway), but it definately does *something*...and I was just curious as to what exactly.

Something recent seems to be causing my ipod (5g, 60GB) to wake up ... I recently cleared all settings and at some point later updated to a more recent build and it seems to have started at some point after that combination of events. I'm secretly suspecting the ipod shutdown fix that went in somewhat recently.

I leave my ipod HOLD switch on after shutting down rockbox - I come back a day or so later and boot up the ipod and it boots into the OF ... which it would not / could not do unless it wakes up (when I'm not looking) at boots into OF (since HOLD is on)

Well so I guess another possibility is that it is the OF alarm, it is waking up and booting into OF, and then when I come back to it the OF has already given up on the fast wake and shut down again. - if that happened, would turning on with hold OFF boot into OF, or into Rockbox?

Ok, so I do occasionally use the OF, but just to charge / sync files. But this isn't one of those (I know because each time, I used rockbox in the morning, and then didn't charge/sync anything between then and the next time I turned it on).

Torne - sorry, got lost in the other convo - which 'that' in particular do you want me to try? (setting rockbox wakeup alarm, waking up, then shut down rockbox and see if problem no longer reproducible? or just see if it's still reproducible for me?)

nano 2nd gen, USB HID ON, player mounts as 'removable device' with no files visible in explorer - safely remove hardware, unplug the dock connector and get *PANIC* Stkov dircache...but with USB HID OFF the player mounts as 'RockPod 2g' (my volume lable), explorer views all files and no panic upon disconnect. Anyone know what gives?

Also (nano 2nd gen as well), (when iPod is off) upon plugging the dock connector in the player will not be detected untill the 'select' button is pressed and it attempts to boot and is picked up by the OS...is this normal?

to clarify my last two posts (on further expirimenting): two seperate issues, 1: USB HID ON causes the player to be identified as 'removable device' with no files visible in explorer, USB HID OFF the player is detected as 'RockPod 2g' and files are viewed fine in explorer. 2: Using 'Safely Disconnect Hardware' to unmount the player with DIRCACHE enabled causes a *PANIC* Stkov dircache, with DIRCACHE OFF or if safely disconnect is not used to unmount th

which targets, if any, have a higher-resolution timer of some sort available? for benchmarking things that don't take very many ticks, the resolution of the system timer is too low. i'm having good results on arm11 with pmnc/ccnt, but i was thinking about providing the benchmarking code i'm using for more general purposes, and it would be nice if it worked as accurately as possible...

these dividers seem to be about 17-18% faster on armv4... the armv5/6-specialized versions are only 4-5% faster than the libgcc ones, but they're also smaller as they contain no unrolled loops. on armv5/6 i think it's pretty clear these are worth using in place of libgcc's dividers everywhere as they will save space. perhaps on armv4 they should be used only by things like APE that use division heavily?

also, the algorithms are from the arm system developer's guide, but the code is from scratch - i used a C implementation of the algorithms that i wrote as a reference for the asm. that *should* suffice for copyright issues?

Sparkeater: we are in feature freeze for 3.5. release should be around 2/2. the freeze and release would have happened around xmas but there were developers against freezing because they had work ready to commit soon and/or because there would be fewer developers around during holidays to do the sort of bugfixing work that the freeze is supposed to be focused on.

amiconn: i figured out a trick for making the large dividend case a nice bit faster. it only applies for signed division, though, where the maximum dividend is 1<<31 - just subtract the divisor at the beginning and add 1 to the quotient. does a nice job on armv6 also as with the sign bit of the dividend guaranteed clear one can use smmul w/ the inverse of the divisor instead of umull.

such a register could (or not) be present in the clipv2 controller, so if you notice something like : ldr r1, [structure, offset]; mov r1, r1, lsl #9; mov r0, #register_offset; bl set_reg; it might be: load the number of sectors to be transferred, multiply it by sector size (= 512), and set this register

in sd-as3525v2.c I have copied the list of pl180 registers (which we know): some of them are pretty standard (IRQ MASK, IRQ CLEAR, ARGUMENT, COMMAND, COMMAND RESPONSE) so I've found their offset in clipv2. The other ones might not exist though

GodEater: stripwax was also having problems with his ipod booting into the OF instead of rockbox, *possibly* because of a false alarm wakeup at an earlier time (a symptom of the original version of the fs10107 patch)

Is there documentation somewhere (other than what I have found on the wiki) aimed at new developers to rockbox? At the moment, I'm looking for things related to what the 'Debug', and 'Logf' options are in the advanced build.

domonoky: I'm not really happy with the server info getting saved in the user ini file. IMO it should only be stored in memory, as its volatile information (and gets overwritten on every new startup anyway)

Yay! I have debugging output.. It seems as though if I configure rockbox with the (A)dvanced -> (D)EBUG option enabled, the mini2440 hangs while trying to boot.. But if I leave it off I can use: #define dbgprintf uart_printf

domonoky, I'd be doing a lot better if I understood why my jtag cable works sometimes but other times not.. I have two theories.. One is gremlins, and the other is there is a jtag god who is very upset with me.

AlexP: (and everyone else)... I have a half idea how to handle the theme mishmash with settings... I'm not really sure if or how this will work, but how about a "enable advanced themeing options" setting which defaults to off?

As far as I can see, if you want the sbs to be shown on the WPS without any changes, tell the wps to show it, and leave that bit of the screen empty in the wps. If you want the slightest difference, treat both as totally separate things

TheSeven, I think there's basically two kinds of players supported by meizu_dfu: 1) players that store the OF in NOR flash (like Meizu M3, M6SP) and 2) players that store the OF in NAND flash (like Meizu M6SL, Samsung YP-S3)

There were several problems. The first one is that even on the simulator, Rockbox enforces cooperative threading. The second is that I didn't paid attention to the fact the the ioctl call to ask the driver if there is some work is blocking (well timeout=100ms). So the entire code did blocked for several ms at random rate. Furthermore, as the usb completion handlers are called in others threads, it would require up to 100ms fo

So I basically put the worker thread in a REAL thread (not a rockbox thread) and hopefully I had protected my code against deadlocks so it was only a matter of minutes once the problems was identified.