- Status Closed
- Percent Complete
- Task Type Patches
- Category Operating System/Drivers
- Assigned To No-one
- Operating System All players
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#7457 - Hiding dircache behind a posix API
Hi,
I made this patch with which presents dircache (and normal dir api for targets without it) as a standard posix api.
This avoids confusion in app code, so that devs won’t mistake and use the dircache-disabled api when dircache is enabled, saving some disks spins
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
forgot to add the dir.h file.
Patch and add that file to firmware/include
Apply the patch, ignore the "File firmware/common/dir.c is not empty after patch, as expected" error and remove firmware/common/dir.c
works here
I have never looked into the details of dircache and frankly I think it should work through the normal file APIs without any awareness by the caller of those APIs that it's even there or not. Is that the intent here? It's the impression I get from a quick scan of the patch.