After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 695984 - Add support for Android direct I/O extensions
Add support for Android direct I/O extensions
Status: RESOLVED FIXED
Product: gvfs
Classification: Core
Component: mtp backend
1.15.x
Other Linux
: Normal enhancement
: ---
Assigned To: Philip Langdale
gvfs-maint
: 693538 (view as bug list)
Depends on:
Blocks: 696016 696190
 
 
Reported: 2013-03-17 05:42 UTC by Philip Langdale
Modified: 2013-03-30 23:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Refactor existing read code (7.62 KB, patch)
2013-03-17 05:42 UTC, Philip Langdale
none Details | Review
implement read support (5.02 KB, patch)
2013-03-17 05:42 UTC, Philip Langdale
none Details | Review
Implement write support (11.20 KB, patch)
2013-03-17 05:43 UTC, Philip Langdale
none Details | Review

Description Philip Langdale 2013-03-17 05:42:35 UTC
Created attachment 239054 [details] [review]
Refactor existing read code

The Android MTP stack implements a set of extensions that allow for direct I/O (read/write) on files - rather than only offering download/upload operations.

With these extensions, it's possible to implement the normal read/write methods in the backend API and allow normal applications to interact with files on the device.

This is implemented as a three part patch series:

1: Refactor existing read code for thumbnails to be useful for general reads too
2: Implement read methods
3: Implement write methods
Comment 1 Philip Langdale 2013-03-17 05:42:51 UTC
Created attachment 239055 [details] [review]
implement read support
Comment 2 Philip Langdale 2013-03-17 05:43:07 UTC
Created attachment 239056 [details] [review]
Implement write support
Comment 3 Philip Langdale 2013-03-30 23:29:35 UTC
*** Bug 693538 has been marked as a duplicate of this bug. ***