Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
my123
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
22 ms
·
301.
▲
Intel on Demand
(intel.com)
62 points
by
my123
4y ago
|
100 comments
302.
▲
by
my123
4y ago
Written on top of Metal with some specific private extensions. I guess that they aren’t willing to long-term support those (yet?). I wonder if they are going to make the Apple OpenGL impl run without those as an alternative too…
303.
▲
by
my123
4y ago
Nah, Apple has a very clean Metal paravirtualisation ABI. This allows to decouple the VM from the underlying HW. macOS 12 VMs will run on Mac hardware that doesn't even exist yet, with GPU acceleration.
304.
▲
by
my123
4y ago
For APFS, they did release some docs at: https://developer.apple.com/support/downloads/Apple-File-Sys...
305.
▲
Advertisement in Operating System (2008)
(patents.google.com)
1 points
by
my123
4y ago
|
0 comments
306.
▲
by
my123
4y ago
https://patents.google.com/patent/US20090265214A1
307.
▲
by
my123
4y ago
The AD102 die this gen doesn’t have NVLink on silicon. RTX 6000 Ada Generation doesn’t have NVLink, and neither does the L40.
308.
▲
Upgrading Multi-GPU Interconnectivity with the Third-Generation Nvidia NVSwitch
(developer.nvidia.com)
48 points
by
my123
4y ago
|
21 comments
309.
▲
by
my123
4y ago
They still do it.
310.
▲
by
my123
4y ago
Intel still sells x86_64 CPUs without AVX. See Jasper Lake and Comet Lake Celeron/Pentium.
311.
▲
Apollo – Amazon’s Deployment Engine (2014)
(allthingsdistributed.com)
2 points
by
my123
4y ago
|
0 comments
312.
▲
by
my123
4y ago
Oh it does. (running the ABL application) UEFI alone isn’t exactly useful when you need per device kernels (and associated modules). It’s just one slice of the problem.
313.
▲
by
my123
4y ago
Qualcomm Android phones use UEFI since the Snapdragon 835. With an Android bootloader UEFI app on top to mimic what Android wants on top...
314.
▲
by
my123
4y ago
GPU firmware is not a security boundary on the vast majority of hardware. With app to GPU communication being mediated by the kernel.
315.
▲
by
my123
4y ago
HMM is on the way for a page migration-based impl that works on most hardware and allows seamlessly to use all CPU memory from GPU programs, including mmap’d files. CUDA 12 is going to be fun. CXL 2.0 and earlier just aren’t it because of a
316.
▲
by
my123
4y ago
There are arm64 designs with MMUs but not FPUs. See Cortex-R82. That [1] is wrong too. Tegra Xavier shipped with sequential consistency out of the box :)
317.
▲
by
my123
4y ago
Arm64 allows FPU-less designs. There are some around…
318.
▲
Oculus co-founder makes a VR headset that can kill you
(arstechnica.com)
5 points
by
my123
4y ago
|
1 comments
319.
▲
by
my123
4y ago
Thankfully from the kernel perspective the Galaxy Book Go SoC is pretty well supported because Chromebooks did ship with the same SoC. However, that specific device doesn’t have good support. Would take some developer time to do so… (and no
320.
▲
by
my123
4y ago
You might want to look at nvprune: https://docs.nvidia.com/cuda/cuda-binary-utilities/index.htm... However: > The input file must be either a relocatable host object or static library (not a host executable), a
321.
▲
by
my123
4y ago
Binary slices for each GPU generation. So that it becomes huge quite quickly, despite use of compression.
322.
▲
by
my123
4y ago
Most people don't have AV1 decoders. So not very surprising that pirates too would choose to use HEVC.
323.
▲
by
my123
4y ago
That devkit wasn't intended to be a development but a testing device. But then they made a big mistake: putting Windows Home on it instead of Pro... so that it didn't have RDP...
324.
▲
by
my123
4y ago
x86_64 is covered since Windows 11
325.
▲
by
my123
4y ago
It is desktop Windows afaik. Server Windows is not quite publicly available yet (on arm64).
326.
▲
by
my123
4y ago
Snapdragon Developer Kit was built with a "cost above all" mandate, $219 target pricing but it just wasn't powerful enough. > There is no other supported desktop/CI/etc. solution for Windows on ARM. (Mac mini wit
327.
▲
by
my123
4y ago
For all ARM64 Windows devices, UEFI Secure Boot is end-user configurable. And yes that includes Surface Pro X, Pro 9 arm and this devkit.
328.
▲
by
my123
4y ago
You'll need to wait a bit until a new device tree comes for these devices. Given that support for the ThinkPad X13s with the same SoC is coming along... going to happen pretty soon.
329.
▲
by
my123
4y ago
UEFI Secure Boot can be disabled or put in a custom configuration on all arm64 Windows devices, including Windows Dev Kit 2023.
330.
▲
by
my123
4y ago
Windows Subsystem for Android currently uses the same infrastructure for GPU virt as the Android Emulator (ie command stream encapsulation with gfxstream, virtio-gpu device).
More ›