9front - general discussion about 9front
 help / color / mirror / Atom feed
From: lyndsay <lyndsay@vivaldi.net>
To: 9front@9front.org
Subject: Re: [9front] trident cyber 9525 graphics glitches
Date: Sun, 5 Sep 2021 18:53:30 -0600	[thread overview]
Message-ID: <286d6931-12e4-ac16-2df2-693547c88e71@vivaldi.net> (raw)
In-Reply-To: <B79A0DBF404ADDC6923F2F0C56C2FC18@wopr.sciops.net>

This is a multi-part message in MIME format.
--------------ED92217CFCC97BA67B1C1856
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

ok, sounds doable... i'll do some work on that tomorrow. i'm pretty sure=20
it would have been using vesa (1.0?) on windows xp, which was installed=20
on it before i demolished it to make room for plan 9, so i think there=20
*is* a way to get it working. apparently the source code for xp is out=20
there, so if linux fails me, there's that too!

i just modified /lib/vgadb, yep. i attached the patch and i did also try=20
to submit a pull request to the main repository but i have no idea if it=20
went through and my git on this pc is broken and has outdated=20
credentials anyway, so it might be better if someone who knows what=20
they're doing just commits it instead =F0=9F=98=85

- lyndsay

On 9/5/21 6:08 PM, qwx wrote:
>> 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

--------------ED92217CFCC97BA67B1C1856
Content-Type: text/x-patch; charset=UTF-8;
 name="cyber9525.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="cyber9525.patch"

294a295
> 	0xC70C5="TVGA BIOS KTT 6.0"             # Cyber 9525 / Satellite 2250CDT


--------------ED92217CFCC97BA67B1C1856--

  reply	other threads:[~2021-09-06  1:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-05 17:30 lyndsay lastname
2021-09-05 22:52 ` qwx
2021-09-05 23:18   ` lyndsay
2021-09-06  0:08     ` qwx
2021-09-06  0:53       ` lyndsay [this message]
2021-09-06 21:29         ` qwx
2021-09-21  4:11       ` lyndsay
2021-09-21  5:06         ` unobe
2021-09-21  9:17         ` qwx
2021-09-21 14:45           ` lyndsay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=286d6931-12e4-ac16-2df2-693547c88e71@vivaldi.net \
    --to=lyndsay@vivaldi.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).