FPGA Central

References: <474ecfeb$0$27127$[email protected]>
In-Reply-To: <474ecfeb$0$27127$[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 071202-0, 02/12/2007), Outbound message
X-Antivirus-Status: Clean
Lines: 16
Message-ID: <4752b468$0$5104$[email protected]>
Organization: les newsgroups par Orange
NNTP-Posting-Date: 02 Dec 2007 14:34:33 CET
NNTP-Posting-Host: 90.41.189.31
X-Trace: 1196602473 news.orange.fr 5104 90.41.189.31:64704
X-Complaints-To: [email protected]
Bytes: 1965
Xref: number1.nntp.dca.giganews.com comp.arch.embedded:267528 comp.arch.fpga:138740 comp.compression:79070 comp.lang.vhdl:67808 sci.electronics.design:863033

Denkedran Joe a écrit :
> So my idea was to put the question to all of you what to do in case of
> uncompressibility? Any ideas?

Hi,

Generally, a compression algorithm may be optimized for a type of data, or for a
"packet" of data (ie with dynamic table building huffman compression, with
different algorithms for video, sound or exe files, etc).

If you can find two (or more) complementary algorithms (or sets of fixed
parameters for a single algo) that covers the whole flows, you can dynamically
switch between them, without transmitting the parameters.

The known of the data flow may help you. Ie, if you may have to transmit an
already compressed packet, your problem may have not any solution.