Originally posted by ldesnogu
View Post
Announcement
Collapse
No announcement yet.
Apple M2 vs. AMD Rembrandt vs. Intel Alder Lake Linux Benchmarks
Collapse
X
-
Originally posted by mdedetrich View Post
In my case they turned on when running JDK 8 under rosetta (couldn't get a native ARM version of JDK 8 working on mac)
- Likes 1
Leave a comment:
-
Originally posted by ldesnogu View PostThe SIMD code I ran made them turn on quickly (within one or two minutes IIRC). Turning on the 4 Neon units on the high perf cores is stressing the beast! That being said I never had any throttling, the fans do their job. In fact I find that machine too cold to put it on my lap.
Leave a comment:
-
Originally posted by ldesnogu View PostI won't dispute your argument that Apple M1/2 are not fully ARMv8 compliant as I'm not sure of two things: AArch32 is not available at EL0 (I don't think it's the case but I might be wrong), and I'm not sure Arm disallows the removal of AArch32 from ARMv8.
I haven't read the developer docs in question but in summary its definitely optional, not only from actual reality of how the chips are built but also the fact that pretty much all compilers treat it as optional but most critically its nothing specific to Apple's ARM chips.
Leave a comment:
-
Originally posted by mdedetrich View PostI also have an M1 pro 14" and fans only go on when stressing CPU for around an hour. Also a developer
Leave a comment:
-
Originally posted by ldesnogu View PostIf that really pissed Apple off, don't you think they would have done as Sony did with the PS3? Just lock the bootloader and the machine is tied to signed OS images. That doesn't mean they'll help porting Linux, but I don't think that irritates them.
Regarding MBA and the lack of fan, a huge proportion of MBA users will never notice. They just browse, listen to music, write mails and so on. As a developer, a fanless Mac is not an option and I got myself an MBP M1; fans almost never turn on even when I compile large codebases. I nonetheless need those fans as I sometimes run heavy SIMD multi-threaded code and that pushes the CPUs enough that active cooling is needed.
Don't forget, most people here are not average users and what we want is not what the vast majority of users want
Source: Asaha Linux, the guys porting Linux to M1/M2.
I also have an M1 pro 14" and fans only go on when stressing CPU for around an hour. Also a developer
- Likes 2
Leave a comment:
-
Originally posted by arQon View Post
Then I phrased it poorly, sorry. What I was saying is that the vast majority of Mn laptops are not going to developers, they're going to users for whom a low-end laptop (not Chromebook-tier, but certainly not a 5950 with a 3080 and 64GB) would be exactly as viable other than in at best battery life, and that they're being bought not because their users have any need for that level of portable power, but because they're middle managers who "have to" have better equipment than the peons, that sort of thing. That is, that for the majority they're status symbols / rewards / etc first, and pieces of "necessary" technology either second or not at all.
IOW, you may be one of the exceptions, but you *are* the exception, not the common case.
With Macbook Air you are right, with Macbook Pro you are dead wrong, that entire demographic is mainly creatives/programmers.
Like if you go to a facebook/google campus/office you will see like 80%+ of programmers have a mac. Even if you look at projects like home-brew (macos specific package manager) and see the ridiculous number of installs if has this is quite obvious
Leave a comment:
-
Originally posted by Dukenukemx View PostThe reason Linux is being ported is because people want it and it pisses off Apple, just like it pissed off Sony to get to see Linux on the PS4 and we all know how well Sony likes Linux on their consoles. Historically Apple created its software from open-source projects, but Apple's developers rarely contribute much code back. Microsoft contributes more code to Linux than Apple ever has. Apple is a shit company.
Regarding MBA and the lack of fan, a huge proportion of MBA users will never notice. They just browse, listen to music, write mails and so on. As a developer, a fanless Mac is not an option and I got myself an MBP M1; fans almost never turn on even when I compile large codebases. I nonetheless need those fans as I sometimes run heavy SIMD multi-threaded code and that pushes the CPUs enough that active cooling is needed.
Don't forget, most people here are not average users and what we want is not what the vast majority of users want
- Likes 2
Leave a comment:
-
Originally posted by qarium View Postdude you earned your fool status the hard way.
credit is given to the people who earns it...
no i am 100% sure i do not want any mobile device like smartphone or tabled or notebook with a fan.
i did see so many devices go down because of dust alone no thank you.
so really no thank you.-.. i do not want a mobile device with a fan.
This is why I got big into cooling because too often computers die from heat. Heat is the # 1 killer of computers. It's not always the CPU or GPU either. You don't want anything to get hot enough to burn your finger. Running a CPU to 95C+ is not good, and it doesn't matter if Apple says it's OK. Every manufacturer says it's OK, and it's always wrong. The only difference here is that Apple purposely lets them get hot because Apple cares more about aesthetics than functionality.
The fact that the M2 Macbook Air slows down means it needed a fan. This was even an issue on the M1 Air's that people found creative ways to make it better.
dude i do not buy these M1/M2 apple devices and the reason is the bad linux support.
but apple can always hire people and fix the linux drivers for this hardware.
Last edited by Dukenukemx; 12 August 2022, 02:22 AM.
Leave a comment:
-
Originally posted by Anux View PostI think it was stackoverflow but can't find it right now. Witch is not the end because I never claimed it to be true. I made a hypothetical guess and mentioned it to explain my way of thinking.
You mean the one that has nothing about missing backwards compatibility in it?
So a section describing how v4/5 and v6 legacy behave different from v6 and v7 on an ARMv7 chip proves its not backwards compatible?
Note that ARMv6 had a compatibility bit to enable the same behavior as ARMv5, but it was removed from ARMv7 thus making some ARMv5 software not portable to ARMv7 and hence ARMv8.
Here is an interesting document describing this difference (and others): https://www.riscosopen.org/wiki/docu...ility%20primer
Stop being ridiculous, that guy worked for Arm's Application engineering group. He writes actual ARM code, not just a call center dude.
From that you can find me on LinkedIn and see what I do. And that doesn't prove I'm always right, I'm not. It just proves your argument is stupid or given my work you'll have to admit that I'm always right
(And I'm not speaking for Arm, all of my posts are personal opinions.)
I guess another link from the net won't convince you either? http://landley.net/aboriginal/architectures.html#arm
Or maybe an example, do you have a RasPi?
I've got the Pi3 (v8 with 64 bit) and I can install a ARMv6 compiled Raspbian, Michael did a test here maybe 2 years ago so you don't have to take my word for it.
Edit: Sorry the test was v7 vs 64 bit https://www.phoronix.com/review/raspberrypi-32bit-64bit but if you have a RasPi >= 3 or know someone you can download the old raspbian vor v6 and run it.
You're right, so my claim that Apples M1/2 is not standard ARM v8 will only hold true if they didn't implement A32 and T32 at EL0. Some guys on the net say no: https://news.ycombinator.com/item?id=27277351 but i can't find a definitive answer on Apples dev-sites.
- Likes 2
Leave a comment:
Leave a comment: