View Single Post
Old 05-29-2025, 01:55 PM   #7
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,030
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by AmarettoWill View Post
Same thing here on PW1. I'm not an expert, but I think that the issue is that newer kindles are on armhf architecture which is hard-float, and older kindles are on armv7l architecture which is little-endian. This version of crawl is built for armhf, so you get these errors on older devices - so no, you didn't mess anything up.
Almost correct. Kindle firmware from 5.16.3 uses hardware floating point while Kindle firmware below 5.16.3 uses software floating point. Nothing to do with big vs. little endian.
DNSB is online now   Reply With Quote