![]() ![]() I do not have a M1, but the task manager screenshot in the other thread suggests a CPU usage of just 4,2% when Imager is run under Rosetta 2: #235 (comment) Instead of running native arm code on our Raspberry Pis let’s just emulate Intel code instead. Given that the Raspberry Pi ALSO uses an arm chip this shouldn’t be considered a radical position I wouldn’t think. I no longer have it installed on my Apple Silicon Macs as if I wanted to run Intel/x86 code I’d own a computer with an x86 chip. I would suggest doing a search on Google for reviews on Rosetta 2. I don't run Rosetta 2 on my Apple Silicon Mac as it is a battery and resource hog. There also may be many users who want an Apple Silicon native build as well. My M1 MacBook cost about half that, not that it’s at all germane to my original post: Raspberry Pi Imager should work on every available platform feasible. Not everybody can shelve out $ 2000 for the latest MacBook Pro. So the easy solution have separate builds and post them in the release section, that is what other devs do.Īnd there may still be users using that. Main problem is that if we switch to universal build releases that would require dropping support for the older Mac OS X 10.13 edition. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |