You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently RELEASE tries to mount any partition from USB storage devices regardless real filesystem tag in such order:
vfat
ntfs
msdos
If any of those mounts will succeed then partition is being accepted for media playback if fail then try mount as next filesystem until all of them fail.
On BCM default Linux kernel supports at least those two filesystems on USB storage devices:
jfs
ext3
Both are used by RELEASE for DVR (AKA Time Machine) in Brazillian TV models but not being mounted on other models.
I would like OPENRELEASE to be able to mount and use for media playback at least ext3 fs (if hard to do as additional mount try) then I would like to sacrifice 'msdos' for 'ext3'.
On Saturn 6 and 7 platforms there are tests with custom kernel that supports even more filesystems so possibility to extend such functionality in OPENRELEASE (via config file?) would be very apreciated.
The text was updated successfully, but these errors were encountered:
Currently RELEASE tries to mount any partition from USB storage devices regardless real filesystem tag in such order:
vfat
ntfs
msdos
If any of those mounts will succeed then partition is being accepted for media playback if fail then try mount as next filesystem until all of them fail.
On BCM default Linux kernel supports at least those two filesystems on USB storage devices:
jfs
ext3
Both are used by RELEASE for DVR (AKA Time Machine) in Brazillian TV models but not being mounted on other models.
I would like OPENRELEASE to be able to mount and use for media playback at least ext3 fs (if hard to do as additional mount try) then I would like to sacrifice 'msdos' for 'ext3'.
On Saturn 6 and 7 platforms there are tests with custom kernel that supports even more filesystems so possibility to extend such functionality in OPENRELEASE (via config file?) would be very apreciated.
The text was updated successfully, but these errors were encountered: