From nobody Fri May 19 11:44:46 2023 X-Original-To: freebsd-current@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 4QN4tr1VhDz4Brmr for ; Fri, 19 May 2023 11:51:32 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx1.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QN4tr0jwXz4ZQL for ; Fri, 19 May 2023 11:51:32 +0000 (UTC) (envelope-from agh@riseup.net) Authentication-Results: mx1.freebsd.org; none Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4QN4l23r22zDqp2; Fri, 19 May 2023 11:44:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1684496686; bh=+6/eaNUvczV5BOa9ccZumd6C+biLPm/h125fV7xyo9o=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=LspGeUnqPRnmmqblG7O3yuGTUYsUlm2yR0+dIYGfl5PCXwY5LRCQSDcpX7S7qCGQn n0duOcRwzkPGVMmUBKTZAKpSHIW3o3/vbORXWvg5++RAPxxskMUbcTSaXkmgAMDdNf iELHgHgv4pjTbxqIa7Cpb+7/3ymQMqbl1qQuASeQ= X-Riseup-User-ID: 7F04CAF1699DB17BF9B4557E7574FE39CAD61ADA63F7AA6EF996607E7A8F3AF0 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4QN4l226VTzJq7q; Fri, 19 May 2023 11:44:46 +0000 (UTC) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Date: Fri, 19 May 2023 11:44:46 +0000 From: Alastair Hogge To: Tomek CEDRO Cc: Ivan Quitschal , freebsd-current@freebsd.org Subject: Re: photo/video on tty console with the new VT/framebuffer In-Reply-To: References: <61502414be8f34256b0f93e8b20d4362@riseup.net> Message-ID: <8f8c2c3563290a705517d5edb8b2acd3@riseup.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QN4tr0jwXz4ZQL X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 2023-05-19 11:30, Tomek CEDRO wrote: > On Fri, May 19, 2023 at 1:28 PM Alastair Hogge wrote: >> As long as those packages support DRMKMS and does your GPU, you can to a >> degree. I noticed video works for mpv and games/sdl, tho, I cannot get >> input working. I tried the Doom 3 port, and watched movies with mpv all >> from the vty just a couple of months ago. > > Yeah, I have input problem too, maybe worth investigating as this is > really neat feature to have gfx with no Xorg :-) It is worth investigating! In a long dead ago project, the input, events, and displays were all integrated into the vty and mux'd from there. The kernel provides evdev devices now, and there is a library, tho I do not know how to get vt(4) to integrate with evdev, or if the library is the way to do it? Any other ideas?