path: root/docs
diff options
authorDaniel Stenberg <>2007-05-19 15:16:05 +0000
committerDaniel Stenberg <>2007-05-19 15:16:05 +0000
commita2c940795068738a46a5a10ccd5b8e55729d5005 (patch)
tree4c1e727fb8b982bacdcce882254f929cfea9f40b /docs
parent5922ab4eccf357db6e0440b44dbedf10b7b289c9 (diff)
introducing KNOWN_ISSUES to list known issues/bugs that are known but not
likely to be fixed soon git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657
Diffstat (limited to 'docs')
2 files changed, 23 insertions, 0 deletions
diff --git a/docs/FILES b/docs/FILES
index 21f2faf0a8..6eab98d824 100644
--- a/docs/FILES
+++ b/docs/FILES
@@ -13,3 +13,4 @@ NODO
diff --git a/docs/KNOWN_ISSUES b/docs/KNOWN_ISSUES
new file mode 100644
index 0000000000..db36ae5835
--- /dev/null
+++ b/docs/KNOWN_ISSUES
@@ -0,0 +1,22 @@
+This is a list of known "issues" in the current Rockbox.
+These are flaws/bugs we know of that are not likely to be fixed within a
+reasonable time so we list them here and close the bug tracker entries for
+FS#894 - When the complete playlist fits in the mpeg buffer, and the playlist
+ is played multiple times, the tracks are reloaded from disk multiple times
+ instead of loaded only once.
+FS#2147 - It's a bug in the MAS. It starts bitshifting data on occasion. High
+ load on the MAS makes this behaviour more likely (high recording level, high
+ quality setting, high sample rate). It's impossible to avoid, but there are
+ plans to implement a recording 'framewalker' that checks recorded data and
+ restarts recording when the MAS starts delivering bitshifted data.
+FS#4937 - A constant rhythmic ticking noise occurs in the right
+ channel. Believed to be related to our slow I2C implementation, and occurs
+ when the battery status and/or realtime clock are updated (the battery is
+ read at up-to 2.5hz and the clock at up-to 1hz). Nothing is going to change
+ with it until someone spends a lot of time analyzing the portalplayer's I2C
+ control registers, or finds a datasheet for the damned thing.