All Projects

Here’s a reorganized version of rockboxdev.sh. It’s 25% smaller and collects most of the target-specific information in one location.

It also installs all binaries to /usr/local/bin by default, to avoid having to change the path.

Here’s a first shot at making our target names consistent everywhere.

The names are the company/linemodel column from http://rasher.dk/rockbox/targetnames.php

In addition to these two patches, files in download.rockbox.org need to be renamed as well.

The same thing as  FS#9797 , but for PP5022 and PP5024.

Frequencies used are 20 MHz and 80 MHz.

Applicable targets: C200, E200, HDD1630, Ipod Mini2g, Ipod Nano, Ipod Video, SA9200.

Currently, boosting on coldfire involves waiting for PLL lock which can take as much as 10ms.

This patch changes the boosting to just toggle the clock divider and not change the PLL frequency, and thus not having to wait for it to stabilize. This makes the boost near instantaneous.

The MCF5249 docs can be interpreted to say you’re not supposed to do this, but they are not conclusive. My limited testing showed no side effects so far.

In order to get clean clock dividers, the patch also changes the operating frequencies from 124/45 MHz to 112/22 MHz. The “default” (idle) frequency is unmodified in this patch and still uses PLL bypass, but is used so rarely it shouldn’t have much impact.

Zero-wait boost opens up possibilities for more efficient cpu management in Rockbox. Coldfire is the only platform where we are not sure this is possible.

Ideally, someone who uses an Iriver player as their daily player should run this patch and see if any side effects pop up.

The current watermark handling is quite hardcoded at 512KB, which is a problem for targets with a small file buffer.

It is also of course not optimal for battery performance.

This patch instead calculates the watermark based on the bitrate of the last file in the buffer and the measured harddisk spinup time.

(This code is not ready for commit.)

We upgraded to Flyspray SVN on november 27, which has fixed most (all?) of the previously reported problems.

Submit new flyspray problems as comments to this task.

I’ll delete comments when they are fixed, keeping only unsolved issues listed.

Sections of the manual marked \setting{} cannot be searched in xpdf.

Here’s a snapshot of my “unified makefile” work in progress.

I’m not asking for bug reports. I am far from done. If you have opinions about the concept as such, though, feel free to comment.

The current state is that it builds the core completely (no plugins or codecs) and links it fine on ipod video, but nothing else.

If you want to play with other targets, remove/comment out the STARTUP(crt0.o) line in the app.lds file for that target.

Current state of my USB implementation. Configuration/enumeration/setup works, but the bulk input (OUT) endpoint doesn’t trigger any interrupt so the usb-storage commands are not received.

This is a “meta bug” where we can collect all issues/bugs/problems with the new flyspray version.

Simply create a new comment for each issue. Try to include an url where the problem is visible.

I’ll delete comments when they are fixed, keeping only unsolved issues listed.

This patch adds a crude key click by turning off and on the dac,
generating a short pop, every time a key is pressed.

I have
only tested this for the recorder, so I would appreciate feedback
from player users. Is it useful? Could it be better?

There’s
not a whole lot we can do about the sound, unfortunately. We can
make several consecutive pops, making a longer sound. However
we can not make a high-frequency beep, since the dac is controlled
over a slow i2c link. The highest frequency possible only sounds
like a coarse noise, so I opted for the single discreet pop
instead.

Sometimes, some directory and file names
show up as garbage.

This does not happen for everyone.

Newer harddrives have multi-megabyte buffers
(some as much as 16MB) that we should use to
increase time between spin-ups.

The theory is that when we spin the disk up, we
first fill our RAM and then keep reading from the
disk without storing it in RAM. The effect is that
we preload the disk buffer so that the next time
we read data, it is taken directly from the buffer
and we can possibly avoid spinning the disk.

One problem is that we need to know the buffer
size of the disk. AFAIK the size can not be read
from the disk.