[Pfspd-users@sf.net] Cpfspd code update

[Bram R. <bra...@nx...>]

Dear pfspd community,

Recently Reinout Verburgh experienced a serious application crash when
trying to use extra components with subsample factors of 240x135.
We found that this is simply not supported by the pfspd file format,
as only two decimal digits are available to store the subsample factors=
.
However, good error checking should have prevented the crash
and simplify debugging.

For this reason, new errors are introduced as stated in the
following fragment of the readme file:

- New errors are introduced to catch header values that cannot be
  represented in the pfspd file format: P_TOO_MANY_IMAGES,
  P_ILLEGAL_INTERLACE, P_ILLEGAL_COMP_SIZE, P_ILLEGAL_LIN_SBSMPL,
  P_ILLEGAL_PIX_SBSMPL, P_ILLEGAL_PHSHFT.
  In order to support the new errors, all defines related to
  header formatting are moved from cpfspd_low.c to cpfspd.h:
  P_SNR_IMAGES, P_SNR_COMPON, P_SNR_FD_RECS, P_SNR_AUXDAT_RECS,
  P_SBYTES_REC, P_SENDIAN_CODE, P_SAUX_HDR_RECS, P_LEN_GLOB_STR,
  P_SIMA_FREQ, P_SLIN_FREQ, P_SPIX_FREQ, P_SACT_LINES, P_SACT_PIXEL,
  P_SINTERLACE, P_SH_PP_SIZE, P_SV_PP_SIZE, P_LEN_GLOB_ATT,
  P_NUM_GLOB_RECS, P_SLIN_IMAGE, P_SPIX_LINE, P_LEN_COMP_STR,
  P_STEM_SBSMPL, P_SLIN_SBSMPL, P_SPIX_SBSMPL, P_LEN_COMP_ATT,
  P_STEM_PHSHFT, P_SLIN_PHSHFT, P_SPIX_PHSHFT.

The code is committed into the repository.
Developers, please update your sandboxes.

Regards, Bram.
--
Bram Riemens, Senior Principal
NXP Semiconductors / Corporate I&T / Research
Email: bra...@nx...
<--- New address and phone since June 2007 -->
Phone: +31 40 27 25910; Fax: +31 40 27 44639
High Tech Campus 32 (floor 1, office 140)
5656 AE Eindhoven, The Netherlands

The information contained in this message is confidential and may be
legally privileged. The message is intended solely for the addressee(s)=
. If
you are not the intended recipient, you are hereby notified that any us=
e,
dissemination, or reproduction is strictly prohibited and may be unlawf=
ul.
If you are not the intended recipient, please contact the sender by ret=
urn
e-mail and destroy all copies of the original message.=