- Status Closed
- Percent Complete
- Task Type Bugs
- Category Operating System/Drivers
- Assigned To No-one
- Operating System iAudio X5
- Severity Medium
- Priority Very Low
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#5399 - X5 OF not aware of RB usb changes
Context:
I’m using one of the X5 CVS builds from last weekend (about May 13th),
with the dual booting bootloader (first version, I think).
Problem:
If I manage files with USB while under RB and subsequently boot into
the OF, it doesn’t reflect the filesystem changes.
I think there must be a flag that the OF USB program sets, so that
when the OF boots, it knows to do a filesystem scan. (The OF takes
ages to boot after I’ve attached a USB cable).
Ideally, RB should set this flag (or whatever) anytime the filesystem
is changed in a way visible to the OF file browser. If that’s
inconvenient, then I suggest that RB should always set it.
2006-05-21 23:32
Reason for closing: Invalid
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
This bug report is only valid in the
context of dual booting. The dual boot
bootloader is not official, so any bugs
relating to it should be reported to its
author, not here.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
The preloader passes two flags to the OF: one is the RTC alarm and the other is always set to zero.
I’m not sure how the OF knows when to scan HDD for changes, but I guess it has to do with checking last access date;
The entire USB mode is handled by the ATA-USB bridge, so I don’t think there’s anything to do here.