Replies: 11 comments 9 replies
-
100% about moving forward, supporting more recent configurations. Dropping everything that makes weight (like tvOS) |
Beta Was this translation helpful? Give feedback.
-
Yes, minimize clutter! You can always use an old release if for some reason you need arm32. |
Beta Was this translation helpful? Give feedback.
-
arm64 for all platforms including windows Drop armv6 / armv7 / i386 - 100% |
Beta Was this translation helpful? Give feedback.
-
As for the RPI I feel the same way as @armadillu |
Beta Was this translation helpful? Give feedback.
-
Android will be the exception, need to support armv7 for that platform for sometime, however new cmake build systems make that easier |
Beta Was this translation helpful? Give feedback.
-
Yes arm64. Have been wanting to use 64 bit OF on Pi and similar. Use OF on Linux mostly, and quite a bit on OSX. Not interested in Windows or Android. |
Beta Was this translation helpful? Give feedback.
-
ARM64, since Pi Zero (2) is now also that. Perhaps also some sort of Firmata example for the Pico. I would like to help out - is there an effort underway, or yet to be decided? |
Beta Was this translation helpful? Give feedback.
-
I'd be interested in hearing other folks' experiences, but I find each oF major version on Raspberry Pi has always required a corresponding new RPi OS version, and not all Pis can run all OS versions, so this doesn't break the pattern. imo the only catch is we need to warn people with RPi 2s specifically to check their CPU--that one was sold in both 32-bit and 64-bit versions. |
Beta Was this translation helpful? Give feedback.
-
I am also interested in this issue. |
Beta Was this translation helpful? Give feedback.
-
My understanding is, since 64-bit OSes and apps use more RAM, on a very
RAM-constrained system like the Zero (512MB) you're hitting the SD card
swap.
Nick
…On Wed, Jul 31, 2024, 4:05 AM Dan Rosser ***@***.***> wrote:
more likely a bug with gcc versions / target / package optimisation flags
or bloat, if memory is 64 bit on 64 bit it should not be slower
Can you confirm
https://qengineering.eu/install-64-os-on-raspberry-pi-zero-2.html 64bit
slice was installed and running and what FPS difference we talking
I have a Pi 2W I'll test it out soon myself with profiler
—
Reply to this email directly, view it on GitHub
<#7138 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF4IZ5X7X3NO2JOJ3DVCCTZPCZFJAVCNFSM6AAAAABLXZMSXGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJZHE3TINA>
.
You are receiving this because you were mentioned.Message ID:
<openframeworks/openFrameworks/repo-discussions/7138/comments/10199744@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
One question for anybody more in touch with RPI development: were we using GLFW for all architectures before? |
Beta Was this translation helpful? Give feedback.
-
One of the things that has made new releases and maintenance slow and tedious is the shear number of platforms OF is supporting.
As its been several years since our last release thought it would be good to see if we can fully transition from armv6 / armv7 to arm64 for embedded linux platforms like Raspberry Pi.
Rpi 3 and 4 support arm64. It will be a fair amount of work to get our build setup configured for arm64, so I am wondering if we can drop the other platforms? ie: if you want to use armv6 you have to use 0.11.2 but 0.12.0 and newer is arm64 only?
I know @dimitre has been trying out an arm64 PR here:
#7069 ( also a related issue #6770 )
Curious if people who use embedded devices more often have any thoughts?
@madelinegannon @patriciogonzalezvivo @roymacdonald @jvcleave
29 votes ·
Beta Was this translation helpful? Give feedback.
All reactions