diff options
-rw-r--r-- | docs/FAQ | 78 |
1 files changed, 68 insertions, 10 deletions
@@ -248,16 +248,15 @@ A32: In simple terms, the first release was called 1.0 because it had a basic | |||
248 | 248 | ||
249 | Q33: I've heard talk of a 'Rolo'. What is that? (Or 'All you ever wanted | 249 | Q33: I've heard talk of a 'Rolo'. What is that? (Or 'All you ever wanted |
250 | to know about Rockbox boot loaders') | 250 | to know about Rockbox boot loaders') |
251 | A33: The developers have discussed the possibility of a boot loader. (Mainly | 251 | A33: Rolo is our bootloader. Currently it is only available in CVS and daily |
252 | because having one sounds cool, and isn't Rolo just a great name?) | 252 | builds, but will be standard in release 1.4. It works by basically |
253 | The idea would be that a user could use the load to choose between | 253 | having a file with the same extension of the firmware (.ajz on Recorder, |
254 | different verions of Rockbox or the Archo firmware itself. We have a | 254 | .mod on Player) 'run' from within Rockbox. Just scroll to the firmware |
255 | working version of ROLO implimented for the players, and a version in | 255 | you wish to switch to and press play. |
256 | development for the recorders. However, at this time, the patch for ROLO | 256 | |
257 | is not optimal for use and is not part of the main branch of the CVS. | 257 | *Poof* You will reboot to that firmware. (Note that in order to return |
258 | Once this improves and has been tested sufficently, it will become part of | 258 | to Rockbox you may need to reboot manually if the new firmware you loaded |
259 | the main release. Please check the mailing list logs and irc logs for | 259 | does not have a bootloader itself.) |
260 | more information. | ||
261 | 260 | ||
262 | Q34: I was thinking about making the USB a bit more usable. What are the | 261 | Q34: I was thinking about making the USB a bit more usable. What are the |
263 | chances of using the USB port to [play games / share files / list | 262 | chances of using the USB port to [play games / share files / list |
@@ -357,3 +356,62 @@ A46: Well you can follow the full line of emails at | |||
357 | 356 | ||
358 | There you have it. Recommeded by users, decision by dictator. | 357 | There you have it. Recommeded by users, decision by dictator. |
359 | 358 | ||
359 | Q47: Why is there a limit of 400 files in a directory? | ||
360 | A47: We have answered this question numerous times. It is mentioned in the | ||
361 | release notes, and in the mailing list archives | ||
362 | (http://rockbox.haxx.se/mail/archive/rockbox-archive-2002-08/0448.shtml). | ||
363 | But, hey, we wouldn't want people to have to work to get an answer. | ||
364 | (If you are reading this, feel proud, for you are the exception). | ||
365 | |||
366 | We settled on 400 files in a directory because file listings take up | ||
367 | memory on the unit, and we felt that 400 is significantly large enough | ||
368 | for a majority of the populace. We prefer the optiono of limiting | ||
369 | file limits in order to provide a greater amount of memory for buffering | ||
370 | of files being played. | ||
371 | |||
372 | Q48: Okay, I understand your 400 file limit. But why hardcode? Why not | ||
373 | have this be dynamically allocated? | ||
374 | A48: Because it's useless. Dynamic memory is only ever useful if you have | ||
375 | memory consumers (tasks) that run at different points in time, and thus | ||
376 | can reuse the same memory for different purposes. | ||
377 | |||
378 | We don't have that. We must be able to show a big dir, index a big | ||
379 | playlist and play a big mp3 file, all at the same time. They cannot use | ||
380 | the same memory, and thus dynamic memory buys us nothing but extra | ||
381 | complexity. If we used dynamic memory for this, we would get all kinds | ||
382 | of odd bugs. Playlists that only got half-loaded if placed in certain | ||
383 | directories. Parts of the disk you couldn't go to if playing a certain | ||
384 | playlist etc. | ||
385 | |||
386 | We have a number of tasks that consume memory. They can all run at the | ||
387 | same time, using all of their alotted memory. Therefore it is much better | ||
388 | to allocate that memory to them beforehand and not pretend that anyone | ||
389 | else is able to use it. This is standard practice in memory-limited | ||
390 | systems. | ||
391 | |||
392 | Q49: Why is there a 10,000 song limit on playlists? | ||
393 | A49: This is another hardcoded limit. We feel that as bigger disks arrive | ||
394 | that this limit will increase. Because of the way that playlists are | ||
395 | stored, it tends to be a bit more maleable then the directory file limit. | ||
396 | For further detail, look at questions 47 and 48 and replace any instances | ||
397 | of '200' with '10,000'. | ||
398 | |||
399 | Q50: You don't understand! I _really_ need to have more then 400 files | ||
400 | in a directory! | ||
401 | A50: Thats it. I'm sending your email address to the guy that asked | ||
402 | question 25 and tell him that you are a developer. If you don't want | ||
403 | that to happen either let happy coders code, find a better solution | ||
404 | (this means impliment it, document it, and send us the patch), or | ||
405 | try taking some time and organizing your files a bit better. Just | ||
406 | because <insert your favorite file music stealing program here> puts | ||
407 | all your files in one directory does not mean you have to leave them | ||
408 | there! | ||
409 | |||
410 | Q51: Can I ask one more question? | ||
411 | A51: You just did. Thank you for your time. That completes your alotment of | ||
412 | stupid question for the year. Please insert another 35 cents to | ||
413 | continue. | ||
414 | |||
415 | |||
416 | |||
417 | |||