Deprecated: Since 5.0.0: Calling Table::get() with options array is deprecated. Use named arguments instead. /application/src/Controller/ParagraphsController.php, line: 67 You can disable all deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED`. Adding `src/Controller/ParagraphsController.php` to `Error.ignoredDeprecationPaths` in your `config/app.php` config will mute deprecations from that file only. in /application/vendor/cakephp/cakephp/src/Core/functions.php on line 377

Warning: Unable to emit headers. Headers sent in file=/application/vendor/cakephp/cakephp/src/Core/functions.php line=377 in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 65

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 158

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 191

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 191

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 228
Dave's PCF WIP: Paragraphs

2184

Application Managing non-volatile media using multiple error correcting codes
Matter Number Reference Case 1
Created 2/22/21, 12:00 AM Modified 2/22/21, 12:00 AM
Application Number

14076579

Paragraph Number

89

Content

The secondary ECC module 304, in one embodiment, is configured to determine whether at least one ECC chunk encoded with a secondary error correcting code is correctable using the secondary error correcting code. In certain embodiments, the secondary error correcting code may be different from the primary error correcting code described above with regard to the primary ECC module 302. As described above, the primary ECC module 302 and the secondary ECC module 302 may operate on different data (e.g., the primary ECC module 302 may encode and/or decode user data, workload data, client data or the like and the secondary ECC module 304 may encode and/or decode access data), or, in certain embodiments, the primary ECC module 302 and the secondary ECC module 304 may operate on at least a portion of the same data in a nested manner (e.g., the primary ECC module 302 may encode and/or decode each ECC chunk and the secondary ECC module 304 may encode and/or decode a subset of ECC chunks, such as access data, using multiple levels or layers of error correcting codes).

Notes

Added by DJM 2 2021