due to hardware limitations we cannot rely on the OESC error code
before the hardware parsed the initial huffman tree. For this case
we have to add a branch to the EOF handling. we return an errorcode 2
(invalid data) if we where still in the initial phase (bytes_out == 0).
Otherwise we continue wi
On 2025-02-17 02:38, Eduard Stefes wrote:
I came up with an ugly hack:
Thanks, it sounds much nicer than the hack I was thinking of, which was
to redo the entire run in software
Hi,
On Thu, 2025-02-06 at 10:20 -0800, Paul Eggert wrote:
> On 2025-02-05 07:46, Eduard Stefes wrote:
>
> > We think that the only
> > possibility for a problem here, is if faulty hardware updates
> > param->cf
> > incorrect.
>
> I'd rather not worry about hardware going bad, unless the hardware
