Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp5336759pxb; Wed, 19 Jan 2022 16:25:38 -0800 (PST) X-Google-Smtp-Source: ABdhPJwYbaSyKMUTSGJGh70nDScF2dUKBpc0Onj84d66d3y109PC1nAdOOik6HHn1CYbT38a0DJe X-Received: by 2002:a17:903:22ce:b0:14a:4623:60eb with SMTP id y14-20020a17090322ce00b0014a462360ebmr34622566plg.81.1642638338333; Wed, 19 Jan 2022 16:25:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642638338; cv=none; d=google.com; s=arc-20160816; b=xWdbA2tb48MlOJiK9qsavh+RkY05wwQty9UFePWrgyfggsWLKiN20YqPnd6xilW7qQ IThkye2mRXK+7d+2YK2FY6ECtqqIfUWeoeWG429EvPEYWpgDrrROBELzewT8pnPzMxuw udJeL1yinG+swepzrFCaxDKZlVOKdLGHwFtf6vYfqQW/0UUG47/e6dbgF4/OR2QIa78q bBvIntxytA5guwplKIDbUBcHc4p/XqlSCCvcvrG1roAn8VYc6O5W34LA7QsoW6btX6iO d7zGnpwLSV5r4JtY1Ow9a0+zufBeGj6yVM2gVSI/WiqMeWB7fDRKyOzDUf+lRoKMNnOX sLhQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=7pHlcaTRiriHEO8haif3+Ixs0hQTPZKTCLrheKgj/Tw=; b=xn4FyDroHDNOK69tPUjGNBlsW70CxnXh/e8pjKbQLg0m4Yj3HbBfNmFnO7pqASJi6B 34m4HznR7QIGzYfhSKfXjmyl4WgIjquPxN7OdpOGmDasWBOELttyIUGZ0bqkzwa2y4ao P0F5hgoFkoTjIybFCdGAkHNjqaf6GvlCrPPdzWT5wMo7K5efNduotizfxK2tiP8bS0sp vF8qjUntguyf5TcAwZJsftBUzFJVUyBCvVZ7MGHa0n1CKqpv4XuhpO6b7yTjljyo1uv+ 5mgo3tLHMC91X6eNWb2/2QNX5yfKCzqwrVTaRYjqZErY/ZuNfG8vBxyl5eYUDpQGvars TB0A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=KUkihOlT; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k26si1634788pgm.319.2022.01.19.16.25.26; Wed, 19 Jan 2022 16:25:38 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=KUkihOlT; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345496AbiARJQh (ORCPT + 99 others); Tue, 18 Jan 2022 04:16:37 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:34080 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345472AbiARJQc (ORCPT ); Tue, 18 Jan 2022 04:16:32 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642497391; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7pHlcaTRiriHEO8haif3+Ixs0hQTPZKTCLrheKgj/Tw=; b=KUkihOlTFcoF4zz8WOHtBv1RcsVmo690jodjuCGyqgMt/TU9siyfEbWItOLEdFfSazNwpY 5hHz6osu12MMe5RFzZhlzYcDmJOU8rCfGvgPDUPi9orkOmprx/qR0kug0hqqyE7m+nKQMa wDmVmYzlQnEKJ1XDqaiA3wEFyWtwv58= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-402-jWJRqNihNV-Jt4u4Ix0mnQ-1; Tue, 18 Jan 2022 04:16:27 -0500 X-MC-Unique: jWJRqNihNV-Jt4u4Ix0mnQ-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 3BD3E10151E0; Tue, 18 Jan 2022 09:16:26 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.49]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B71D84BC48; Tue, 18 Jan 2022 09:16:17 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id D309318000A6; Tue, 18 Jan 2022 10:16:15 +0100 (CET) Date: Tue, 18 Jan 2022 10:16:15 +0100 From: Gerd Hoffmann To: Helge Deller Cc: Daniel Vetter , Linux Fbdev development list , Sven Schnelle , Linux Kernel Mailing List , DRI Development , Javier Martinez Canillas , Geert Uytterhoeven , Thomas Zimmermann , Linus Torvalds Subject: Re: [PATCH] MAINTAINERS: Add Helge as fbdev maintainer Message-ID: <20220118091615.3ih5n7vhd6tgmnku@sirius.home.kraxel.org> References: <20220117125716.yjwxsze35j2ndn2i@sirius.home.kraxel.org> <70530b62-7b3f-db88-7f1a-f89b824e5825@suse.de> <57d276d3-aa12-fa40-6f90-dc19ef393679@gmx.de> <20220118062947.6kfuam6ah63z5mmn@sirius.home.kraxel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 18, 2022 at 09:20:43AM +0100, Helge Deller wrote: > On 1/18/22 07:29, Gerd Hoffmann wrote: > >> Please correct me if I'm wrong, but text-console emulation/scrolling on DRM is > >> currently unaccelerated and bound to Truecolour modes only, > > > > Yes. Adding support for formats beside argb8888 to the drm fbcon > > emulation shouldn't be that much of a problem though. > > Really? Assuming a graphic card which runs with only 256 colors framebuffer > is easily supported by DRM, and you can use fbcon without using lots of memcpy()? Driver: programming a fixed color cube palette, then use RGB332. fbcon/fbdev emulation: RGB332 support must be added I think. But both argb888 and rgb565 are supported today, so it should not be hard to find the places where you have to add some code to handle RGB332 too. > > Acceleration is harder. The scroll acceleration had issues nobody > > addressed for years, and on modern hardware it is simply not used, which > > is probably the reason nobody stepped up fixing things and it ended up > > being dropped. > > The DRM layer doesn't use scroll acceleration. > More than 30 other existing fbdev drivers use it. Yes. The world shifted from 2d acceleration to 3d acceleration. Modern hardware simply has no classic blitter any more. Which is a problem when it comes to keeping scroll acceleration alive, it is already a very niche use case and it will only become worse ... > > Bringing it back is much more work than just reverting the commits removing it. > > Reverting those commits have no effect on DRM's usage of fbcon. > But reverting those commits bring back scroll acceleration for all others. > I'm trying to find out which patches did apparently fixed such issues > for the REDRAW case. If you have a pointer it would be helpful. IIRC the code had a bunch of races and syzkaller flagged problems. I didn't follow very closely though. take care, Gerd