From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 20262 invoked from network); 6 Sep 2021 00:52:25 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 6 Sep 2021 00:52:25 -0000 Received: from wopr.sciops.net ([216.126.196.60]) by 4ess; Sun Sep 5 20:08:35 -0400 2021 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sciops.net; s=20210706; t=1630886904; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=RyGpQTXq/vPgVgqezIjUP8O3qdWhDE6FE4Q5VEfUeok=; b=C4Ro6sSSlyY46Yt145HFQNBKcMzy2VRpCk9dkCy/zfdADCtF5r1X0HFnQxMesV5MFl7IYd HcJT2dmVeNdcp5pB9ZMloIfqgc8K8PMWrY8shTgG6jj5iiU7ATAQfa9z/rllY20w8MN/uj s+iriA3C5cBIkzJJ+hsTLS5qrU8VNno= Received: by wopr.sciops.net (OpenSMTPD) with ESMTPSA id 85fe4e2b (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO) for <9front@9front.org>; Sun, 5 Sep 2021 17:08:24 -0700 (PDT) Message-ID: From: qwx Date: Mon, 06 Sep 2021 02:08:22 +0200 To: 9front@9front.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: asynchronous virtualized API wrapper shader Subject: Re: [9front] trident cyber 9525 graphics glitches Reply-To: 9front@9front.org Precedence: bulk > oh my god, i can't believe i didn't think of simply trying a lower > resolution. i'm an idiot sometimes. the graphics DO in fact work fine, > and it accepts 24-bit color, using a 640x480 resolution! i would > definitely be interested in trying to debug and fix the issue at the > source if you/others on the list are interested in helping with that, > but i know that's a tall task and probably not a priority for most > people, so just downscaling looks like it will work as a quick > superficial fix. I doubt it occurred to me immediately either :) Do compare drawing performance between 16 and 24bit mode, one may be significantly faster than the other for you. Debugging over the ml is very slow, but I would suggest comparing with linux or some other os to check if vesa works there and if the drivers behave the same way, and if they don't, 1) tracing where vesa fails, and/or 2) tracing where the memory issue comes from in the cyber938x.c drivers (/sys/src/9/pc/vgacyber938x.c functions in cyber938xdev struct and /sys/src/cmd/aux/vga/vgacyber938x.c) and reading the linux or w/e driver... Others may make smarter suggestions. Please send a patch for whatever you modified (just /lib/vgadb?) :) Cheers, qwx