From nobody Wed Jul 10 11:12:00 2024 X-Original-To: freebsd-drivers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WJwDX6RDRz5QFsn for ; Wed, 10 Jul 2024 11:12:12 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [IPv6:2a01:4f8:171:f902::5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WJwDW41G7z46Ly for ; Wed, 10 Jul 2024 11:12:11 +0000 (UTC) (envelope-from crest@rlwinm.de) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of crest@rlwinm.de designates 2a01:4f8:171:f902::5 as permitted sender) smtp.mailfrom=crest@rlwinm.de Received: from [IPV6:2a00:c380:c0d5:1:8426:f32e:7779:a0b8] (unknown [IPv6:2a00:c380:c0d5:1:8426:f32e:7779:a0b8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id EE6B0EA4E for ; Wed, 10 Jul 2024 11:12:01 +0000 (UTC) Content-Type: multipart/alternative; boundary="------------fbUKQPbxpPpximhDBBe06D9P" Message-ID: <65311a51-d8d2-4367-bd30-bc0956e04781@rlwinm.de> Date: Wed, 10 Jul 2024 13:12:00 +0200 List-Id: Writing device drivers for FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-drivers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-drivers@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: What Is FreeBSD Missing? To: freebsd-drivers@freebsd.org References: <2d3dea20-6bcf-49f8-930e-9250988b2d2b@gmail.com> Content-Language: en-US From: Jan Bramkamp In-Reply-To: <2d3dea20-6bcf-49f8-930e-9250988b2d2b@gmail.com> X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.14 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.85)[-0.847]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-drivers@freebsd.org]; DMARC_NA(0.00)[rlwinm.de]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-drivers@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4WJwDW41G7z46Ly This is a multi-part message in MIME format. --------------fbUKQPbxpPpximhDBBe06D9P Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 29.06.24 05:54, Steven Friedrich wrote: > It's missing the Linux magic of routing audio through the video driver > to the HDMI port. Mint, KDE Neon, etc., produce sound out of the HDMI > cable, FreeBSD does not. > You're confusing multiple things. Mint, KDE, etc. are desktop environments that aren't supposed to ship their own custom hardware drivers. Instead the kernel is supposed to have OSS audio drivers for all audio devices including your GPUs HDMI ports. Unless you GPU driver lacks audio support the HDMI port should show up in `cat /dev/sndstat` once the drivers are loaded. At that point you can change your (default) audio device to select the HDMI audio output. I know for a fact that it works with both Intel iGPUs and Nvidia GPUs. --------------fbUKQPbxpPpximhDBBe06D9P Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

On 29.06.24 05:54, Steven Friedrich wrote:

It's missing the Linux magic of routing audio through the video driver to the HDMI port. Mint, KDE Neon, etc., produce sound out of the HDMI cable, FreeBSD does not.

You're confusing multiple things. Mint, KDE, etc. are desktop environments that aren't supposed to ship their own custom hardware drivers. Instead the kernel is supposed to have OSS audio drivers for all audio devices including your GPUs HDMI ports. Unless you GPU driver lacks audio support the HDMI port should show up in `cat /dev/sndstat` once the drivers are loaded. At that point you can change your (default) audio device to select the HDMI audio output. I know for a fact that it works with both Intel iGPUs and Nvidia GPUs.
--------------fbUKQPbxpPpximhDBBe06D9P--