mjtomlin
About
- Username
- mjtomlin
- Joined
- Visits
- 192
- Last Active
- Roles
- member
- Points
- 4,861
- Badges
- 2
- Posts
- 2,699
Reactions
-
Apple Silicon M1 Mac detection of Thunderbolt 3 eGPU gives hope for future support
lkrupp said:Interesting how first generation hardware features are assumed to be etched in stone and immutable. It couldn’t possibly be that Apple wanted to get these entry level machines in the hands of users as son as possible to gauge usage and performance No, no, assume the worst and start ranting and raving about how ALL ASi (current and future) Macs are useless pieces of garbage because these ENTRY LEVEL machines can’t run Windows natively and don't support eGPU. It’s happening on all the major Apple centric tech blogs.
Well, didn't we hear the same ranting and ravings over Apple dropping support for Thunderbolt because the DTK didn't support it?Developer support documentation and later experimentation confirmed that support for non-Apple GPUs wouldn't be enabled in hardware using Apple Silicon, effectively making eGPUs largely unusable.
Yeah, not completely true. The developer documentation does not say discreet (or external) GPUs would not be supported. All it said was to not underestimate the integrated GPU in Apple Silicon. Even the chart (Apple Silicon Mac GPU) these sites, included as proof, shows that Apple Silicon Macs will still support "Metal GPU Family Mac 2" APIs which are used to interface with non-Apple GPUs. -
CodeWeavers gets Windows apps running on Apple Silicon
zimmie said:dewme said:WINE/Crossover is targeting a different set of use cases than Parallels and VMWare. WINE is focused on getting individual apps running across platforms. Basically WINE is installing software shims and adapters to replace only the native operating system dependent calls, libraries, and services that the specific application actually uses with ones that work similarly on the non-native platform. This makes their adaptation, which is not emulation (as the WINE name asserts), very application specific and (in my opinion) very fragile. I say fragile because if the app developer updates their app to use different calls, libraries, or system services on the native platform it will probably no longer work with WINE until an updated set of shims and adapters is built.
I liken WINE somewhat to the way I got my ancient Northgate 101 mechanical keyboard and PS2 mouse to work with a Raspberry Pi. I chained together a full sized DIN-to-PS2 adapter to a PS2-to-USB adapter that handles both the keyboard and mouse. It works because the mechanical interfaces are translated by connector adapters and the electrical signals are translated by a little controller embedded in the PS2-to-USB adapter. Looks kludgy but works perfectly.
Parallels and VMWare emulate/virtualize the entire operating system on the foreign host. This sounds like it would be rather slow, but most Intel chips built over the past decade and a half have silicon level assist that improves parts of the virtualization stack significantly. Also, most modern operating systems including macOS, Unix, Linux, and Windows have various types of abstractions around the underlying hardware from applications, i.e., hypervisors, that greatly improve virtualization. All of this underlying hardware and software assist for virtualization greatly improves the performance and robustness of virtualization on these platforms.
Did I mention WINE is not an emulator? In the case of Apple Silicon, Rosetta 2 is providing the required x86 emulation/virtualization.
Meanwhile, Parallels and VMware emulate most of a whole computer, except for the processor. You have to install a whole operating system in them. x86 instruction privilege levels are tracked in "rings", with lower numbers being more privileged. Ring 0 was the most privileged for a while, then they started adding negative rings with VT-x, VT-d, and so on (the "silicon level assist" mentioned above). Windows now tries to grab all the negative rings on boot to prevent malware from grabbing them. I suspect the reason Rosetta doesn't officially support virtualization is related to processor support for these negative rings. Specifically, I bet Apple doesn't feel like faking ring 0 and below, and without faking the hardware support, performance would be really bad. It may not even work at all, because the Intel processors Apple has shipped have always supported a few of the negative rings. It's possible Parallels and VMware don't have their own software emulation for those unsupported instructions in the Mac versions of their products.
It's all emulation, or virtualization, or pathological lying. The difference is what is being lied about.
WINE is just an alternative API layer (aka compatibility layer). It does not emulate the OS at all. It takes Windows apps and hooks standard Windows API calls into their API's. It is very similar to how NextStep apps were able to run under different operating systems. It also why Rosetta is so fast, because the macOS APIs exist on both Intel Macs and Apple Silicon Macs...
The model is...
Application -> API -> Operating System
As long as the application only uses what's available in the API... as you move those API's to different operating systems, those applications should be able to make the move as well. -
M1 Mac mini teardown reveals smaller logic board, non-upgradeable RAM
sflocal said:mjtomlin said:sflocal said:If Apple really wanted to, they could probably get the Mac mini's footprint to be slightly larger than what an AppleTV box is. I bet when it comes time to redesign the chassis, it's going to shave a lot of heft off the next gen ASi systems.
Only if they remove the power supply. At least 25% of the inside is taken up by it.
There's a lot more than just the SoC that draws power in a computer; SSD, WiFi, etc. Also the AppleTV doesn't have to supply power to external devices... USB4 spec requires at least 7.5W of power per port to external devices, and can go up to 100W (to power external displays). The power supply has to provide for that. So even though the M1 may max out at 20W-25W, the Mac mini may need to be able to supply more than 100W just to supply the USB busses.
The M1 being used in the mini (and 13"Pro) is a fluke. As I've stated before, I do believe this was designed specifically for the Air, and as a "bonus" side effect of its high performance - they decided it could be released in other entry level models - and that the next SoC (M1X) was designed for both of those systems along with the 21.5" iMac. -
M1 Mac mini teardown reveals smaller logic board, non-upgradeable RAM
caladanian said:No gigabit option any longer?
Not for this SoC. I personally believe the M1 was originally intended for the MacBook Air only, so Apple may have kept PCIe support to a minimum. As several Apple engineers have stated, they were shocked by the performance they got, and I think that's when they decided to also use it in the 13" Pro and mini. Maybe hoping his limitation might keep higher end users from purchasing these "low end" models.
I think the next SoC will increase expandability, then maybe we'll get 10Gb Ethernet, more Thunderbolt ports, support for more displays and possibly support for eGPUs. -
M1 Mac mini teardown reveals smaller logic board, non-upgradeable RAM
entropys said:The RAM is separate to the SOC? Interesting.
Yes and no. The actual logic is separate from the RAM, but they are both in the same SoC package. All the photos we have seen clearly showed this. I’m not sure why the article thinks “RAM is soldered to the motherboard”. The SSD sure is, but no, the RAM is part of the M1.