add a new crc32 api like crc8 or crc16 which has many variants.

Seems like even in different versions of python the CRC32 is different:

https://stackoverflow.com/questions/30092226/calculate-crc32-correctly-with-python

And also when the file is bigger than 2GB:

python/cpython#105967

@xiaoxiang781216 I think we need to convert our default crc32 to become compatible with Linux and move the current to a different name and use it on existing subsystems that requires the current implementation.

What do you think?

I am fine with this change since the compatibility with other popular POSIX OS is always my top priority.

Is the difference just init value or polynomial itself? Maybe keep the default crc32, there is some reason why exactly that variant has selected (I don't know what), but blindly chaning the defaults would break it for people already using it.

There is no one "correct crc32", but many variants. If the difference is just init value, you can use "crc32part" directly to calculate it starting with whatever init value you want.

Hi @jlaitine actually it is not a blindly change, many people faced this issue in the past, but I agree it could break other people code and probably this modification will require changing the NuttX major number. As you said, there is not a "correct crc32", but it is important to select a default variant compatible with Linux.