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.

hello, does anyone know if rockbox *could* run on an ARM like STM32F103? question is really that it has no external interface for ram. I have one of these on a dev board and ram is all it is missing :(

JdGordon: with the last version of the playback rework patch, is the problem with the garbled id3 info supposed to be solved or does this still happen sometimes? i haven't seen it, but i had some lines of garbage in my scrobbler.log and was wondering if this could be related.

Unhelpful sees that pictureflow is (c) Nico_P, a Jonas Hurrelmann (who is not in IrcNicks)... Nico, when you get a chance, how much do you know about its renderer? because i'm tempted to rewrite much of it, primarily to have something that i can understand well enough to be able to optimize/bugfix it

hrm, well, then, i guess it depends on whether this business with rays[] etc comes from Ariya, Jonas, or Nico. i'll have to try to figure out if it's an optimization of "how i would do this"... because it seems to work, but i found things that don't make much sense while trying to sort out pixelma's divide-by-zero report

the "distance" that is stored in each slide appears to be centered on the plane in which pixels map 1-to-1 with screen pixels, but then that is added to LCD_HEIGHT, and other values with cryptic names are divided by it...

how can i set where files are recorded to? (i've read the manual, the 'clear recording directory' seems like it might be what i want but a) that's a scary name, i don't want to clear out any of my recorded files and b) i don't want to reset the location, i want to *set* it)

Looking at pacbox again, the #ifs could be quite complicated to exclude the correctly... But I think some more targets could be added quite easily - e.g. greyscale ipods, including the Mini (with a little cropping)

If somebody cared enough, the font could be replaced with one that scales better on such targets (including the sprites for the pacman/ghosts/fruit etc)... I think the Mame port in IPL does that, at least for the sprites.

evilnick is reminded of "The problem with WMA is that the existing open source WMA implementation is using floating point arithmetics, something that the CPU in the iriver can't deal with. We need to convert all calculations to fixed point, a rather tedious and complicated task. Someone with a clue needs to step forward and do this. The problem is that people with a clue don't use WMA."

I've used it on my Gigabeat S, my iPod video, and my iriver H340. The performance as a codec is very good on all three targets, but the author of the patch has been concentrating on making it a viewer plugin.

Download a supported version of the Iriver firmware for your Iriver iHP100, iHP115, iHP120, iHP140, H120 and H140 from the Iriver website, links can be found on IriverBoot. Supported Iriver firmware versions currently include 1.63US, 1.63EU, 1.63K, 1.65US, 1.65EU, 1.65K, 1.66US, 1.66EU and 1.66K. Note that the H140 uses the same firmware as the H120; H120 and H140 owners should use the firmware called ihp_120.hex. Likewi

Llorean: I still think it would be a good idea to finally have a Bootloader v7 for the H100, though. It's been a long time in coming that we can finally remove the iriver firmware from the H100 entirely.

kugel: I don't know when it broke. I haven't updated RB for a couple of weeks. Yesterday I did and saw some weird things. FM stations can't be switched, status bar is drawn ... or not, and once the next song info was not shown

amiconn, pixelma: IIUC, chaining is for inheriting keymaps. If a specific context does not define an action for a key it can be inherited from the parent context. And since the main menu should be callable from everywhere it would make sense to define it in some top level context which is inherited by almost all other contexts

I still don't understand what you would gain from chaining to the wps context - the current version worked so far, I can't fully understand why wps buttons is more logical (only for left/right and ajusting volume) because there are some specialties in both screens. And I think it could *possibly* make the code/keymaps more complicated for other targets

I think the contexts should only be chained when the are logically related. The fact that some actions in one "specific" context are the same as in another is a sign that contexts are not designed properly. I.e. there could be some contexts that are only there as a base for inheritance but not used "as is" in any screen.

rasher: some of the gentoo dev docs have stacks and stacks of arguments about how evil using a project's version-control repo for builds is... i can't say that most of them hold much weight, really, but they're sold pretty hard.

volkmar: seriously, we don't have broken code in our repository very often, and there's basically nothing else that builds against rockbox that you have to worry about breaking after updating it. there's really no reasonyou can't build latest.