FreeCalypso > hg > freecalypso-tools

comparison doc/TIFFS-IVA-usage @ 1012:11391cb6bdc0

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch from fixeria: doc change from SE K2x0 to K2xx Since their discovery in late 2022, Sony Ericsson K200 and K220 phones were collectively referred to as SE K2x0 in FreeCalypso documentation. However, now that SE K205 has been discovered as yet another member of the same family (same PCBA in different case), it makes more sense to refer to the whole family as SE K2xx.
author Mychaela Falconia <falcon@freecalypso.org>
date Mon, 23 Sep 2024 12:23:20 +0000
parents 3152e23399a2
children
comparison
equal deleted inserted replaced
1011:6d9b10633f10 1012:11391cb6bdc0
189 tiffs <...> catino [-v|-h] ino 189 tiffs <...> catino [-v|-h] ino
190 190
191 Just like regular cat, but takes an inode number instead of a pathname. Can be 191 Just like regular cat, but takes an inode number instead of a pathname. Can be
192 used to cat the old content of deleted or overwritten files. 192 used to cat the old content of deleted or overwritten files.
193 193
194 Support for SE K2x0 extended filenames 194 Support for SE K2xx extended filenames
195 ====================================== 195 ======================================
196 196
197 As explained in the SE-K2x0-FFS article, Sony Ericsson K200/220 phones use 197 As explained in the SE-K2xx-FFS article, Sony Ericsson K2xx phones use
198 TIFFS as their flexible data storage mechanism, but they also made their own 198 TIFFS as their flexible data storage mechanism, but they also made their own
199 non-standard extension to TIFFS in terms of extended UCS-2 filenames. 199 non-standard extension to TIFFS in terms of extended UCS-2 filenames.
200 200
201 In order to allow listing full FFS trees from SE K2x0 phones with tiffs ls and 201 In order to allow listing full FFS trees from SE K2xx phones with tiffs ls and
202 possibly also extracting them with tiffs xtr, we have made the following hackish 202 possibly also extracting them with tiffs xtr, we have made the following hackish
203 extension to our TIFFS IVA: whenever either of these two commands encounters an 203 extension to our TIFFS IVA: whenever either of these two commands encounters an
204 "extended" filename (one which fails standard TIFFS filename validity checks but 204 "extended" filename (one which fails standard TIFFS filename validity checks but
205 has a terminating NUL that allows the name and data portions of the chunk to be 205 has a terminating NUL that allows the name and data portions of the chunk to be
206 separated) in the visible tree walk, our tool replaces it (for the purpose of 206 separated) in the visible tree walk, our tool replaces it (for the purpose of