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.

I must make a build for my brother, 8. I am applying a ton of patches to do this. One thing I need to do is make rockbox simple as possible and that requires taking out untested coad such as the usbstack (which I found doesn't work).

amiconn: I'm taking a break from this 5002 CPU crache (sic) thing. I've gotten nowhere in finding a solution. I know this much: 1) 100% dependent on having caching running. I can test by simply not setting certain bits in the control register and leaving the compiled bin otherwise identical. 2) 0% relevant regarding number of cores allowed to run.

if you want to make windows forget about ever seeing the device, you need to run the add/remove hardware wizard, and check the 'show hidden devices' or whatever they call it nowadays. That will show all devices it knows of. Then select the right one and remove. Too bad you need to run the wizard again and again if you need to remove multiple

Zagor: I want to improve current stack, by allowing to switch at runtime between serial/storage... driver. Have you thought about any design for this? I have stated working on this topic: http://nopaste.snit.ch:8001/11668

Zagor: so you want to have that all "dirvers" have functions e.g. usb_serial_init() and in the usb_core we have a switch, which evaluates the current driver to use and calls then e.g. usb_serial_init() ?

austriancoder: by the way, I was thinking about whether we really want a setting for driver or if we should use a set_configuration call to select the right one. using a call avoids all user confusion.

austriancoder: only one configuration can be active at any one time. the usb command set_configuration is used to select which configuration to use. a hypothetical logf_reader or debug_reader tool could send the set_configuration to activate serial mode.

there was someone (TMM) starting to work on an Iaudio 7 port and it's already part of configure. I believe something went wrong with the player though and I don't know of anybody else working on that target

jmspeex: I've been trying to get my head around how to do the forward transform in dca, they use a qmf, but they have a 512 taps long filter, and there is a qmf called pqmf but the specs also mention PQF

Hm - did anyone get back to roxfan[zzz] able to read a certain high density bga flash chip? Was on irc a couple days ago (rio karma). If so wonder if that's a feasible approach for ipod nano 2g/classic

bertrik - true, but will all .data be contiguous? For example, if I put static bool dummy CACHEALIGN_ATTR at the top and bottom of apps/plugins/pacbox/z80.c , is that going to ensure that ALL the (non-ibss) data used by the z80 engine is going to live at addresses that cannot map to cache entries used by anything else?

I'm not sure what firmware version my player first had, since it got corrupted and I never checked. But I then reinstalled/updated with 1.01.06p and the Sansapatcher at least worked without me doing anything special on the player

stripwax_: Wouldn't it be better to wait and see if we end up getting bmp resizing in the core? They were talking about a higher quality resize than the existing bitmap resize patch used, last I heard.

preglow - is having high quality bmp resizing in the core a necessary precondition for applying the sliding_puzzle bitmap patch (in presumably a modified form that makes use of that bmp resizing in the core)

moos: I just don't understand why it's necessary. Genlang does the hard work, and marks points for translators to take care of. If you're doing francais.lang by hand, I understand why it's helpful to have it in the same order, but that's not the norm

rasher: WE ALWAYS UPDATED THE LANGUAGES THIS WAY BEFORE, BUT THEN AGAIN THAT'S NOT A PROBLEM, JUST A DETAIL, BUT DON'T SAY THAT WE ALWAYS MADE THIS BEFORE, SINCE ALL TRANSLATIONS WAS MADE THIS WAY AND THIS SINCE THE START IIRC

rasher: then please "read and shut up" too what I said you, I didn't claimed that *you* broke any convention, I just made the error to report you one observation that I saw with patches submitted and used the tool. Sorry for the annoyance then

no changed things, that's just due to langv2 changes but before translators didn't use genlang for update the translations, then we always used for easabilty same order that's english for easy compare and differences checking. Now if we say that we don't follow the english order, that's not a problem