lkml.org 
[lkml]   [2020]   [May]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
SubjectRe: [PATCH 2/2] docs: lzo: fix incorrect statement about distance zero for EOS
Date
Looks good to me, thanks

Dave

On 22/05/2020, 15:11, "C. Masloch" <pushbx@ulukai.org> wrote:

The encoded distance bits are zero, but the distance that is
calculated from this is actually equal to 16384. So correct
this statement to read that the 0001HLLL instruction means
EOS when a distance of 16384 is seen. This matches with the
description of the instruction itself later on.

Signed-off-by: C. Masloch <pushbx@ulukai.org>
---
Documentation/lzo.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/lzo.txt b/Documentation/lzo.txt
index f839d104d..dc9e876cb 100644
--- a/Documentation/lzo.txt
+++ b/Documentation/lzo.txt
@@ -65,9 +65,9 @@ Description
generally encoded in the last two bits of the instruction but may also be
taken from the last two bits of an extra operand (eg: distance).

- End of stream is declared when a block copy of distance 0 is seen. Only one
- instruction may encode this distance (0001HLLL), it takes one LE16 operand
- for the distance, thus requiring 3 bytes.
+ End of stream is declared when a block copy of distance 16384 is seen,
+ encoded in a certain instruction (0001HLLL) with the H and D bits all zero.
+ It takes one LE16 operand for the distance, thus requiring 3 bytes.
.. important::

--
2.26.2


IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
\
 
 \ /
  Last update: 2020-05-22 17:23    [W:0.048 / U:7.748 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site