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.

Someone just replied in flyspray with a H10 5 GB. they said it got rid of rebooting right at start up, but performance seemed "a bit sluggish"... But, with the past patches, some people have reported great improvement, and some people said sluggish, so I would say my patch fixes problems with kernel_on_cop_7

Put I'm kinda tired of receiving emails letting me know that yes, running the iPod 30mhz faster does in fact allow playback and the menus to run more smoothly, when I just want to know when they get the PP5020 scaling bug fixed.

uh, I thought that task was about the 5020 scaling bug. WTF is w1ll14m doing changing the focus of the thread. w1ll14m I notice you are here, so don't think I am talking behind your back, but it seemed to take w1ll14m long enough to realize the 5th gen didn't have a 5020.

But even though I addressed that, people are still trying to talk about increasing the CPU speed. And unlike the forums, I can't just "split" it, and then say "This is what this task is about, stay on-topic or I'll remove your posts"

I'd be tempted to close it, open two others, and block-paste relevant comments lump-sum into the two new tasks. Removing cruft like "I've been playing mp3s for about 1.5 hours nonstop now." in the process.

bluebrother: Well, I was looking for a way to easily printout nearly everything to read through. I've never fully sat down and read things, but I wanted to say, compare the install sections for each, etc.

I was looking for a way to printout all the optional sections of the manual easily. Basically a "full" manual, assuming that you had one target that had *every* feature. Plus all the unique install processes.

How long it takes for the batteries to die can depend a lot on whether you're using the equalizer, whether you have headphones plugged in or not, whether you press any buttons (or light up the backlight), etc.

decayedcell: in fact i didn't, it was just probably an I/O port direction register and changing its value activated internal pull-up resistors or something like that and dropped the backlight brightness a bit

rp-: Not yet - I'm going to try reverting r12000 tonight and see if that helps. Disabling writing didn't help, nor did adding extra delays in the LCD. It looks like a loop is hanging in the main thread

pondlife: I believe the fixes to *how* boosting happens are relevant to the Kernel_On_Cop patch since the current theory is that maybe the state of the coprocessor matters. It seems the KoC patch plus an earlier boosting fix actually seem to solve the problem, though full testing would be nice.

pondlife: We really *really* should be testing with working coprocessor support though, just because that's how it's meant to be using, and proper implementation of the coprocessor may already be the cause of the problem. And even if it's not, that's the final conditions under which a fix will have to work.

Server message 505: 'logbot :Private messages from unregistered users are currently blocked due to spam problems, but you can always message a staffer. Please register! ( http://freenode.net/faq.shtml#privmsg )'

Server message 505: 'logbot :Private messages from unregistered users are currently blocked due to spam problems, but you can always message a staffer. Please register! ( http://freenode.net/faq.shtml#privmsg )'

10:43:55

Nick Nakedis now known as Hadaka (i=naked@62.142.249.112)

10:43:56

***

Server message 505: 'logbot :Private messages from unregistered users are currently blocked due to spam problems, but you can always message a staffer. Please register! ( http://freenode.net/faq.shtml#privmsg )'

I thought the same as you at the start - i.e. we just want to start and stop a single thread on the cop. But if we do that, we would need a special sleep() function for the COP, and #ifdefs for threads that run on the COP on PP targets, and the main CPU on other targets.

Hello. I'd like to repeat my question from yesterday 17:35:23: What happens to the hidden disc sector after updating to a RB version where settings are stored in cfg files? Can the sector be removed so that there will be no tracks of RB if I delete RB specific files?

amiconn: It seems to yield a lot during a flush at normal priority to where explicitly yielding there only causes more loss of ground. There's no explicit yield at all in pcmrec_flush but when boost it may be too aggressive.

anyone got any ideas on the latest Apple install forum post. I seem to recall someone else describing the same issue recently - but don't recall if we managed to get their computer to recognise the iPod again properly ? (I think this was posted in the mailing list somewhere?)

If it didn't end up yielding a fair amount the screen would freeze up till the flush was over. If it boosts the screen crawls. Overcompensating one end of this recording thing could possibly cause the observed problems from the other end.

In order to cause maximum stress, the block sizes and alignments for each block are chosen randomly (using a second prng - the standard rockbox rand() - so that mechanism doesn't interfere with sequence generation)

I am thinking about adding some logging facility to it, which would log the write block boundaries & alignments for each block, and print an "expected data/actual data" comparison if it hits a difference

amiconn: The files on the Sansa are different, and it looks like it is to do with the alignment - the same sequence of bytes occurs in both files, but offset by 2 bytes. There are only 10 mismatches in the 300Mb, though

Hmmm... it's aligned writing which is breaking the Sansa. If I remove that, the stress test passes. That suggested to me that declaring the registers as ints instead of shorts had messed things up - but fixing that doesn't make the test pass.

so if that setting is set to "No", what happens when inserting the USB cable while holding REC? nothing seems to happen (except that an icon in the status bar changes), so what's the pointing in having it set to "No"?