my123

6 ms·

1.
Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA(global.fujitsu)
2 points by my123 1d ago|0 comments
2.
by my123 3d ago
Yeah talking about the (vendor-preferred) compute part here Vulkan's SPIR-V dialect is substantially different from the OpenCL one, notably with the former having structured control flow. They're incompatible between each other.
3.
by my123 3d ago
oneAPI is effectively an Intel-only platform not a standard. Yes they have implementations on top of CUDA but they're maintained by... Intel. They didn't get buy-in for cross-vendor collaboration
4.
by my123 3d ago
> Intel uses SPIRV iirc They're migrating away from SPIR-V to their own, Intel PISA: https://discourse.llvm.org/t/rfc-upstreaming-the-pisa-backen...
5.
by my123 3d ago
> TSO yeah that one is more messy on Windows, with extensive reliance on RCpc... > and status flags it's part of FEAT_FlagM(2) - has been there since the Snapdragon 8cx Gen 3 on the Windows side
6.
by my123 8d ago
it's available in retail (the foldable phone variant) in mainland China since today
7.
by my123 10d ago
It's an old comment. iirc it's a documented feature now - FEAT_E2H0, https://support.arm.com/documentation/109697/2025_12/Feature... And it was retroactively defined to be allowed starting from Armv
8.
by my123 24d ago
Windows has a stable syscall ABI today officially, for supporting down-level containers: > https://learn.microsoft.com/en-us/virtualization/windowscont... > Decoupling the User/Kernel boundary in Window
9.
by my123 29d ago
One thing in the story is that the SPU - the secure enclave on Qualcomm chips that is separate from just running on TrustZone on the main processor - is only available on Snapdragon 8 and X tier products. It's market segmented away fro
10.
by my123 1mo ago
> Finally, we will continue to progressively open-source more of the Mojo language, as well as components in MAX that we have built with it. Our commitment remains unchanged – we will open source the Mojo compiler and toolchain in 2026.
11.
by my123 1mo ago
Windows NT on PowerPC was an actual product, although running in 32-bit mode.
12.
by my123 1mo ago
A big chunk of the problem is planning/political: https://en.wikipedia.org/wiki/Purple_Line_(Maryland) > A March 2025 report by the Maryland comptroller's office found that permitting and legal fees for th
13.
by my123 2mo ago
And for the Jetsons btw still uses device tree with custom kernels but at least it's UEFI from Orin onwards. For Jetson Orin and later: You can download an ISO from https://developer.nvidia.com/embedded/jetpack&#x2
14.
by my123 2mo ago
No the Spark uses UEFI + ACPI Regular Ubuntu or Fedora ISOs do work out of the box Just needs the Nvidia GPU driver install afterwards (And the realtek 10gbe module oot, or blocklist if not used)
15.
by my123 3mo ago
It was true a long time ago for some particular cases, but is not true since quite some years now.
16.
by my123 3mo ago
> but the only build targets are i386 and amd64 arm64 ReactOS boots all the way to desktop with it being on the way to upstream too.
17.
by my123 3mo ago
NVIDIA's recent Nemotrons tend to be open training data and code. Probably as a base to use by people buying NVIDIA hardware to train their own.
18.
by my123 4mo ago
For the DGX Spark and OEM variants a big issue is that the ConnectX-7 is just not designed to have low power idle but instead to be efficient when loaded. NVIDIA already lowered power draw at idle by 18W with a currently out of tree driver
19.
by my123 4mo ago
Windows CE late in its lifetime (CE 6.0) had that go away with per-process address spaces.
20.
by my123 4mo ago
Not much public yet about VRE virtualisation (which includes SEP) at this point. > whose only purpose would be to capture those HVCs quite expensive because you get to trap ~ all EL0 -> EL1 priv transitions through the virtualisation
21.
by my123 4mo ago
> HCR_EL2.HCD That's not ideal because of: > Any resulting exception is taken to the Exception level at which the HVC instruction is executed. instead of trapping to the hypervisor > I've looked at how different hyperviso
22.
by my123 4mo ago
It was a kernel panic for Tahoe. Anything between macOS 12 and 26 wasn't tested so releases in-between might have more issues. The userspace reboot after FileVault password entry acts a bit oddly with QEMU input devices so you might ne
23.
by my123 4mo ago
FYI: https://patchew.org/QEMU/20260324204855.29759-1-mohamed@unpr... There's some randomness around Tahoe for FileVault and it crashing because Data is detected as not encrypted (and that's not OK on bare met
24.
Qualcomm Hexagon V81 HMX Programmer's Reference Manual [pdf](docs.qualcomm.com)
2 points by my123 4mo ago|0 comments
25.
by my123 5mo ago
> They ditched that once Rosetta support on ARM Macs was good enough to run x86_64 VMs, as apparently all they cared about was supporting Docker on Macs... Was a research project gone out of hand, arm64 macOS wasn't on the radar and
26.
Arm Helium Technology Reference Book (2023) [pdf](github.com)
2 points by my123 5mo ago|0 comments
27.
Drawbridge: What SQL Server on Linux is built on (2021)(threedots.ovh)
2 points by my123 5mo ago|0 comments
28.
by my123 5mo ago
Redacted
29.
by my123 5mo ago
XNU has this oddity: https://github.com/apple-oss-distributions/xnu/blob/f6217f89... Redacted from open source XNU, but exists in the closed source version
30.
by my123 6mo ago
After Power9, IBM became uncompetitive multi-core performance against mainstream server CPUs - both x86 and Arm. They didn't keep up with the rise in core counts. And the single thread side isn't that good either, but SMT8 is a qu

More ›