On 4/26/20 4:42 PM, Jon Elson wrote:
On 04/26/2020 01:01 PM, andy pugh wrote:
On Sun, 26 Apr 2020 at 17:00, Jon Elson <[email protected]> wrote:
Also, this bug would have affected all 2.7.x versions
installed on a 64-bit kernel. Should we
backport the fixed version to them?
Do you think that it is important enough to prompt an incremental 2.7
release? If not then it won't get out to users anyway.
Well, I don't know what standard distros of 2.7.x were made with 64-bit
kernels. If none,
then there's no problem. It then could only affect people who built
from source, and we can tell
them how to fix it.
We ship 2.7 on the following platforms ("i386" is Debian-speak for
32-bit x86, "amd64" is 64-bit x86):
RTAI:
Debian Wheezy (i386)
Ubuntu Precise (i386)
Ubuntu Lucid (i386)
Uspace (rt-preempt or vanilla):
Debian Stretch (i386 and amd64)
Debian Jessie (i386 and amd64)
Debian Wheezy (i386 and amd64)
Ubuntu Precise (i386 and amd64)
Ubuntu Lucid (i386 and amd64)
If there IS a 2.7.x distro iso file with a 64-bit kernel, then it should
be fixed. This bug is completely
"fatal" on 64-bit compiles, as the encoder rolls over from 0 to
-16777216 counts, causing an
immediate following error. And, this affects all 3 of the Pico Systems
devices.
I'm happy to make a new 2.7 release with this fix.
--
Sebastian Kuzminsky
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
