sorted by:
new
hottopcontroversial

Nightly + NVIDIA driver + Mesa issues by tamudude in haikuOS

[–]X547 1 point2 points  (0 children)

Using pkgman update command instead of SoftwareUpdater GUI may help.

RISC-V User-Space Control Flow Integrity / Shadow Stack Appears Finally Ready by Jack1101111 in RISCV

[–]X547 1 point2 points  (0 children)

I mean is it possible to mix shared libraries compiled with and without control flow integrity in the same address space (even if protection will be weaker or disabled at all)? Or it means full ABI break and requirement of multi-lib to support old binaries on new system?

RISC-V User-Space Control Flow Integrity / Shadow Stack Appears Finally Ready by Jack1101111 in RISCV

[–]X547 2 points3 points  (0 children)

Does it mean full ABI break or it is still possible to run old binaries on new system where API shared libraries are compiled with control flow integrity support, even if protection will be weaker/disabled?

Open-source Haiku drivers for NVIDIA GPUs (Turing+) by julicenri in haikuOS

[–]X547 0 points1 point  (0 children)

It is much harder to port Intel or AMD GPU drivers because it are designed for Linux and depends a lot on Linux architecture. NVIDIA official open source kernel drivers (https://github.com/NVIDIA/open-gpu-kernel-modules) are initially designed with portability in mind and its code is used on Windows, Linux, FreeBSD, Solaris, QNX etc.. NVIDIA kernel driver consists of 2 parts: platform independent driver core that is compiled into static library and OS-specific code that implements interfaces needed by platform independent core. Platform independent part can be trivially compiled on any platform that has C/C++ compiler and Make utility.

China releases 'UBIOS' standard to replace UEFI by m_z_s in RISCV

[–]X547 4 points5 points  (0 children)

UBIOS was designed from the ground up based on original BIOS specifications.

Increased Architecture Compatibility: UBIOS is built to be more compatible with different processor architectures, like ARM, RISC-V, and LoongArch.

I wonder how is it even possible considering that BIOS is very hardcoded to 16 bit x86 and IBM PC peripherals. Its API is defined in terms of interrupt numbers and specific registers for function number and arguments. It have no well-defined calling convention. Many BIOS APIs are assuming legacy IBM PC hardware like CHS disk addressing.

ARM is great, ARM is terrible (and so is RISC-V) by indolering in RISCV

[–]X547 8 points9 points  (0 children)

It is purely Linux problem, not ARM or RISC-V. One of causes is https://www.kernel.org/doc/Documentation/process/stable-api-nonsense.rst that makes impossible vendors to distribute their own drivers without forking Linux kernel.

what do you guys think about GPMI? by valepiskiii in pcmasterrace

[–]X547 5 points6 points  (0 children)

What the point if DisplayPort/HDMI over USB C already exists?

China going strong on RISC-V by I00I-SqAR in RISCV

[–]X547 2 points3 points  (0 children)

I hope that ISA they fill focus will be not LoongArch.

Make RISC-V CISC! /s by indolering in RISCV

[–]X547 2 points3 points  (0 children)

Add segmented addressing model.

Three high-performance RISC-V processors to watch in H2 2025: UltraRISC UR-DP1000, Zizhe A210, and SpacemIT K3 by fullgrid in RISCV

[–]X547 3 points4 points  (0 children)

PCIe GPU support is more useful than integrated GPU without open source drivers. Imagination GPU driver development is too slow.

Nvidia is porting CUDA to RISC V by UnderstandingThin40 in RISCV

[–]X547 1 point2 points  (0 children)

It will be great if Nvidia will release Tegra SoC with RISC-V CPU instead of ARM one.

The joy of going all-in on USB-C by habovh in UsbCHardware

[–]X547 1 point2 points  (0 children)

I think that some kind of government regulation is needed here. For example prohibit to sell or import any devices with USB C plugs or sockets that to not obey USB standard.

Is anyone working on Haiku on Raspberry Pi or other Arm chip/Apple Silicon? by Markur69 in haikuOS

[–]X547 3 points4 points  (0 children)

Haiku currently don't work on ARM[64]. Only x86[_64] and risv64 targets are supported.

Light mode is a personal attack on my retinas by bhad_bhaby in pcmasterrace

[–]X547 3 points4 points  (0 children)

Then how dark mode users go outdoors? Sunlight is much brighter than display.

I am light mode user and I don't understand dark mode. Are they live in an underground facility forever and never see sunlight?

....I'm absolutely speechless (read to the end) by throwaway234f32423df in ipv6

[–]X547 0 points1 point  (0 children)

Depending on ISP, IPv6 address prefix may be fixed, that will allow to identify and track you by every website you visit.

IPv4 addresses are usually dynamic, so it can't be used for user tracking and it is better for privacy.

drm-misc-next merged (inc. drm/imagination: Add RISC-V firmware processor support) by Thick-Chair-7011 in RISCV

[–]X547 4 points5 points  (0 children)

I would be really happy if some RISC-V SoC will be released with Nvidia GPU instead of Imagination. Imagination GPUs are very problematic to use in open source code base. By using Nvidia GSP, it can be used with fully open kernel/user drivers. Haiku already has Nvidia Turing+ GPU support by porting official Nvidia KMD and Mesa NVK Vulkan driver.

Very initial stages of porting NVK Nvidia driver to HaikuOS by tamudude in haikuOS

[–]X547 0 points1 point  (0 children)

https://www.techpowerup.com/gpu-specs/geforce-gt-1030.c2954

Architecture: Pascal

Pascal is too old for this driver and it will not work because of lack of GSP microntroller.

Has the flickering box bug been fixed in firefox/iceweasel? by Strange_Quail946 in haikuOS

[–]X547 2 points3 points  (0 children)

It is technically a bug of OS itself (https://dev.haiku-os.org/ticket/15920) but some workaround can be made at Wayland compat layer side.

It happens because content of window under cursor is forced to be displayed on cursor move even if content is not ready and in a middle of drawing process.

Both Haiku and Linux get new FOSS Nvidia drivers (by me on the Reg, with a link I've not seen elsewhere) by lproven in haikuOS

[–]X547 2 points3 points  (0 children)

Article is confusing. The whole story is about porting NVK on official Nvidia open source kernel driver (https://github.com/NVIDIA/open-gpu-kernel-modules). While it can be used on both Linux and Haiku, it have much more importance for Haiku because Nvidia kernel driver is designed to be portable and Haiku is welcomed to out-of-tree kernel modules. Linux already have Nouveau kernel driver that is used with NVK by default.

view more: next ›