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=-2.6 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,NICE_REPLY_A autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28696 invoked from network); 21 Sep 2021 04:34:25 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 21 Sep 2021 04:34:25 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Received: from smtp.vivaldi.net ([31.209.137.12]) by 4ess; Tue Sep 21 00:18:11 -0400 2021 Received: from localhost (localhost [127.0.0.1]) by smtp.vivaldi.net (Postfix) with ESMTP id 5C6C9BD05B for <9front@9front.org>; Tue, 21 Sep 2021 04:11:11 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.vivaldi.net 5C6C9BD05B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vivaldi.net; s=default; t=1632197471; bh=ZA8TqWIBoP9sg86+q7UrFx5m8UQ49//NsClCSc/IDts=; h=Subject:To:References:From:Date:In-Reply-To:From; b=gnObWWAcv8bJinAIx2bPltOaMCH4EgxGncwWk2zdE/BqMdvcUujPgOuym6Op4lGnE jq+P20c7IRUVpjJHcEIjFavW5i9guAu9c4EcmO53rJm9liaQOOE6/w6IYjeJfHKJyP g5itkq92km2YfInfFJqd0QiKKqZjSwnYoYDD/i6RT/fRb8guTc75D+lwsgG3qvB7ae MdLifsHJoHAwtBCQqxuPRIh3IsJkDRquv5ifMXvNn11+o+IVFWUozWKqXl0HR5SpR+ 3MgVcQgPoozoif/pShtOw5YuJmrHberqNxwQsa8rbwdol6lw7g+W7fInChBciMnqer C90biReZCCOLg== X-Virus-Scanned: Debian amavisd-new at smtp.vivaldi.net Received: from smtp.vivaldi.net ([127.0.0.1]) by localhost (mxo.viv.dc01 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uv3gpt3UZgQd for <9front@9front.org>; Tue, 21 Sep 2021 04:11:07 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.vivaldi.net BEDF1BD03E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vivaldi.net; s=default; t=1632197467; bh=ZA8TqWIBoP9sg86+q7UrFx5m8UQ49//NsClCSc/IDts=; h=Subject:To:References:From:Date:In-Reply-To:From; b=obGuLNmrRbwPduNi2/y5gw5PuQv2iNqGrlSSAZ7AvCjU/GkUUGtLZdDR59kkzaKtA Ann3sq5yMk/z/bMW9mdGvHMo4Dud3Wm1LKlVU4aAd9nMqH2zd4B1rL2NTm0JNI4pwB d7EW5P+rfxZWs92WV3MHLap/mxCwBrjn7CH+7RsWu/KsaoU0obA7jn9CTxxQVpdN5Q Amw1hL07dybQuiOr2fZZRiCXX0q8ddyZdB+fctmh4uB957M/KX0LvqsWf3k4VkbFvl hRxzVutXH08TBFBjspNO8rdA1JZpSkVD8Gs1Bf8e+RKPijtHWyjf2ycRtXB6d67MIx t6NFvUrwriCOQ== To: 9front@9front.org References: From: lyndsay Message-ID: <04dddd48-aaea-7d48-66d8-ffb6ae74520f@vivaldi.net> Date: Mon, 20 Sep 2021 22:11:01 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: polling SOAP over JSON replication GPU controller Subject: Re: [9front] trident cyber 9525 graphics glitches Reply-To: 9front@9front.org Precedence: bulk i have been trying to work further on this tc 9525 issue but i've run into a couple stumbling blocks. i got the book by richard ferraro recommended in vgadb(6) in order to figure out what i'm doing and while i do intend to read at least the relevant parts, it is 1600 pages long so i'm moving slowly. it also is slightly too old and only addresses trident cyber editions up to 9430, which makes it hard to figure out ironclad specifics for the 9525 (especially because according to ferraro, the memory addressing especially differs significantly between versions, so i cannot trust the information there to necessarily be applicable to the 9525). could still maybe infer how it operates from looking at the 3,000(!) lines of bloated terrible xorg code for this driver alone but frankly, i would rather read the entire 1600 pages and spend weeks reverse engineering the card all while lying on hot coals than do that. anyway i had the thought that i should test the graphics with a specific monitor entry in vgadb before trying to slog through the book, because i didn't try that before, only added the did. (correct me if this definitely will not do anything to help; i'm still new to how this all works.) i found an xserver configuration for the same card on a toshiba laptop with the same resolution (not the exact same laptop though), so i'm thinking it might work as a base - https://www.sanpei.org/Laptop-X/Laptop-X/Toshiba_Satellite_4070CDT. unfortunately the vgadb man page does not actually explain how to write a monitor entry, since 6 key fields can, according to it, only be explained by that book. i cannot find an explanation for those from the skimming i've done and they don't seem self-explanatory, looking through vgadb. anyone on this list happen to know where it explains shb/ehb/ht/vrs/vre/vt in the book? or if you don't but you can explain it that's great too. also, qwx, did my original vgadb patch go through ok or did it get lost? i can try to send it again in the git format if you want. thanks ! lyndsay