From nobody Sun Nov 28 16:43:44 2021 X-Original-To: freebsd-hackers@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 3D80918BABA7 for ; Sun, 28 Nov 2021 16:44:07 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4J2DpG3Z02z3q91 for ; Sun, 28 Nov 2021 16:44:06 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f47.google.com with SMTP id m9so18151782iop.0 for ; Sun, 28 Nov 2021 08:44:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OCcSzfr8n1wp+NPsNq4dWQPNoQDf0JaqBuRZQQsSyjY=; b=WJtgffg3nfqKAwACVrR5Soq2qAoiBIuu+5vyqGr8EgFKCQNEXWelw8U55V1Bbx7dED Gw/DcKkMH75rV3Y3ShKb8XIwEL3HAtlTqSGO4bR9QEM17Pm/OAUUf6nDm8Opui1uW24z GmflhOmlxIwib1FzebcUP3vIM2Knjy/mqBkK/LF7S8Fn44vKOeLjN0VQ+02Ez0jl+inX sxESs54fDMJGddqKHQ+7nvRye+0Wtoy0CjK5CGnXfuwfJJlMErT+uR8uwFhWGHOnZXnj l8Wb1yZTb/ma4PpqqDL7Dn2/SmVd1jOTI7c6q6YeCEvcEgAD7W55vxjL4vqK45mucmPO JAXg== X-Gm-Message-State: AOAM532X9xkyz+3KMJf2qMV6xf/ReaPz2nKY5gEcFjTRte7jFS3dBVbt 0m0cI0QCbOvllUofYDh7kaB1HY0D9xQWyTRRB5589jzt/4c= X-Google-Smtp-Source: ABdhPJz+nB/Md+tuqD6ersvaMvgw0iqrYNCfvLXMWhtGaBmQY9VzULfojlxrvbFATJq+eGQ/slqW1PMovTFQg0AjM1M= X-Received: by 2002:a5d:818a:: with SMTP id u10mr50339254ion.140.1638117839471; Sun, 28 Nov 2021 08:43:59 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <20211126160454.3eb827365a02103169ab9adc@bidouilliste.com> In-Reply-To: From: Ed Maste Date: Sun, 28 Nov 2021 11:43:44 -0500 Message-ID: Subject: Re: Reasons for keeping sc(4) and libvgl ? To: FreeBSD Hackers Cc: Emmanuel Vadot , Stefan Blachmann Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4J2DpG3Z02z3q91 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.47 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [0.91 / 15.00]; RCVD_TLS_ALL(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_CC(0.00)[bidouilliste.com,gmail.com]; FREEFALL_USER(0.00)[carpeddiem]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; ARC_NA(0.00)[]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.972]; NEURAL_SPAM_LONG(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.47:from]; NEURAL_HAM_MEDIUM(-0.12)[-0.120]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.47:from]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-ThisMailContainsUnwantedMimeParts: N On Fri, 26 Nov 2021 at 10:45, Stefan Blachmann wrote: > > Main technical reasons why I consider sc(4) essential: > > - vt/vesa.ko break suspend/resume on nvidia cards. To make > suspend/resume work on computers with nvidia, it is necessary to build > a kernel *without* vt/vesa modules. See > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253733 To wrap up this one - this is an issue with `options VESA` / vesa.ko. It is not related to vt(4), which does not use that VESA driver. I have removed `options VESA` from GENERIC now in b8cf1c5c30a5. It serves no purpose when vt(4) is in use, and the kernel module is still available for sc(4) users who want to set a VBE mode. As an aside, the loader can set a VBE mode and vt(4) will make use of that, it just does not support mode changing after boot.