my123

51 ms·

691.
by my123 5y ago
The exposed API for Metal is Obj-C, and the one for DirectX is using COM. (for shaders, MSL is a C++ dialect, but HLSL isn't)
692.
by my123 5y ago
For macOS at Reduced Security, kernel extensions will no longer be supported. fuOS/CustomKC will stay in the long term, and that's what matters for other OSes.
693.
by my123 5y ago
Heuristics are used. For example, memory accesses relative to the stack pointer will be assumed to be thread-local, as the stack isn’t shared between threads. And that’s just one of the tricks in the toolbox. :-) The result of those is that
694.
by my123 5y ago
The extensions present in the M1 are not used at all by Apple’s public compilers. From the perspective of a 3rd-party macOS developer that doesn’t reverse engineer, it’s just a regular arm64 machine. This allows Apple to deprecate/chan
695.
by my123 5y ago
There is some minor breakage, like Apple CPUs enforcing the VHE feature of ARMv8.1-A to be on, and not supporting it being off. But that was like… the sole issue on that front. What you are allowed to do is make extensions with the highest
696.
by my123 5y ago
Not necessarily/really, the custom extensions still need to be enabled by the kernel before they can be used. As such, it isn’t actually an issue.
697.
by my123 5y ago
That’s a single ACTLR bit present in the publicly released XNU kernel source code.
698.
by my123 5y ago
Except if the app has an updater built-in to itself, in which case there is no prompt as far as I remember.
699.
by my123 5y ago
It’s currently in a limited preview, not accessible outright to any AWS customer even.
700.
by my123 5y ago
And the bigger AGX Xavier has a PCIe 4.0 x8 slot at the top, a PCIe 4.0 x4 M2 connector sandwiched in for NVMe and a x1 M2 one for a Wi-Fi adapter. Was among the earliest launched PCIe 4.0 platforms.
701.
by my123 5y ago
It’s too hard/not really feasible today to guarantee SMT safety between VMs. As Lambda is a many-VMs platform…
702.
by my123 5y ago
Much less. Teams where the manager is paid less than the engineers that they manage aren't rare either.
703.
“Intel Software Defined Silicon” Coming to Activate Extra Licensed HW Features(phoronix.com)
7 points by my123 5y ago|2 comments
704.
by my123 5y ago
Modern/Connected Standby is S0ix, which goes out of that convention.
705.
by my123 5y ago
If it’s because of having to map the BARs as device memory, then it’s a problem that will be taken care of. That said, the details of the right approach to work around this isn’t quite ironed out yet. On Apple M1, trying to map the BARs as
706.
by my123 5y ago
For E1, it's because of less aggressive OoO for power saving, and a very aggressive power target of 180mW at 2.5GHz on 7nm. It's within 1.5x of Cortex-A55 perf on single threaded workloads, and with efficiency as the mantra, SMT w
707.
by my123 5y ago
That's not NV related sadly, but applies for all Android TV devices. It's beyond their control... And for PCIe VFs for virtualized GPUs, AMD does _not_ provide it either outside of their datacenter line. Note that if you just pass
708.
by my123 5y ago
In many countries, you aren’t allowed to bundle insurance with a product.
709.
by my123 5y ago
S0ix is the replacement, which allows for connected standby. (see https://01.org/blogs/qwang59/2020/linux-s0ix-troubleshooting ) Connected standby has been the norm on mobile since ages, quite popular in lapto
710.
by my123 5y ago
For QCOM the bindings for the base drivers are stable, and despite them forking drivers, the one for the others generally are - too The biggest concern there is the PEP power management mechanism instead of using what ACPI provides. > Th
711.
by my123 5y ago
Windows doesn't have that issue on Arm, you can just boot the newest Windows on Arm release on a random SoC from the past that (if it's the same arch of course, 32 bit or 64 bit have different drivers) as long as the work was init
712.
by my123 5y ago
> One issue is that unlike x86/x86_64, there is no generalized abstraction platform (similar to BIOS/UEFI/ACPI description tables) that enables "one kernel to rule them all" Windows on Arm devices use UEFI + ACPI
713.
by my123 5y ago
It's locked down on AMD customer APUs, only not forcefully disabled on AMD customer CPUs that do not have integrated graphics. (Ryzen PRO parts have it officially supported)
714.
by my123 5y ago
iOS 15 didn’t drop support for any device supported by iOS 14. Rumours are wrong sometimes.
715.
by my123 5y ago
Going to answer point by point: > That said, we know at least the VMkernel is likely to work on other ARMs, though userspace might not like it if you don't have things like AMX in your CPU, or the SPRR stuff Open-source XNU doesn&#x
716.
by my123 5y ago
> because the M1 SSD controller has not yet been reverse-engineered It has been. Supported in the Corellium tree today and in a tree somewhere for Asahi, on its way to mainline
717.
by my123 5y ago
It does not, once the system has booted, the TPM doesn’t protect you. (For drive encryption purposes)
718.
by my123 5y ago
You can just use NVMe on those, even boot from it. On mine, I don't even consider it as existent. :)
719.
by my123 5y ago
In the first half of next year, Jetson AGX Xavier will be superseded by Jetson AGX Orin at the same price point, which has 12x Cortex-A78AE. Will be quite a nice bump. At the same time, the SW stack will switch to UEFI for the bootloader, i
720.
by my123 5y ago
Yes, because somebody might freak out/panic on an airplane, let them die! What are you even thinking?

More ›