Document exact-release Linux hardware validation

[friidump.git] / docs / README.technical

diff --git a/docs/README.technical b/docs/README.technical
index 058de1600dee0790ec8dbb0beba1e156f064fe5f..c820e863d2e7c55a828c1a21c44c6b8a7d03b2ac 100644 (file)
--- a/docs/README.technical
+++ b/docs/README.technical
@@ -315,9 +315,9 @@ media FriiDump writes this layout:
 
 - output LBA 0..6831: visible DVD-video L0, read from source LBA 0..6831;
 - output LBA 6832..198143: pregame padding, currently zero-filled;
 
 - output LBA 0..6831: visible DVD-video L0, read from source LBA 0..6831;
 - output LBA 6832..198143: pregame padding, currently zero-filled;

-- output LBA 198144..198175: 32-sector game lead-in; FriiDump attempts to read
-  these sectors from the active unlocked/game view and zero-fills only unreadable
-  sectors;
+- output LBA 198144..198175: 32-sector game lead-in, read from unlocked source
+  LBA 0..31; the native libfriidump path zero-fills only a genuinely unreadable
+  sector and records the fallback count;

 - output LBA 198176..3629407: unlocked game/XDVDFS data, normally read from
   source LBA 32 on GDR-8050L, or from the detected XDVDFS source LBA on other
   supported profiles;
 - output LBA 198176..3629407: unlocked game/XDVDFS data, normally read from
   source LBA 32 on GDR-8050L, or from the detected XDVDFS source LBA on other
   supported profiles;


@@ -342,9 +342,10 @@ detected XDVDFS start LBA through LBA 1913920 and prepends a 32-sector game
 lead-in. For single-layer/homebrew-style media it treats the XDVDFS VolumeSize
 field as a byte count and converts it to 2048-byte sectors.
 
 lead-in. For single-layer/homebrew-style media it treats the XDVDFS VolumeSize
 field as a byte count and converts it to 2048-byte sectors.
 

-Both Xbox output styles attempt to read their 32-sector game lead-in from the
-active drive view and zero-fill only sectors that are not readable through the
-selected drive/profile.
+Both Xbox output styles preserve the 32-sector game lead-in from unlocked
+source LBA 0..31. The GDR-8050L reference path fails the dump if this proven
+range cannot be captured; the native libfriidump path retains a counted
+per-sector zero-fill fallback for other profiles or transient read failures.

 
 
 Supported-drive notes
 
 
 Supported-drive notes