9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] vga neomagic 256AV on external display...
Date: Mon, 10 Oct 2005 20:48:21 +0200	[thread overview]
Message-ID: <200510101848.j9AImMC09095@zamenhof.cs.utwente.nl> (raw)

sorry, vga time for me. I'm no good at that (so far).

I'm trying to get a neomagic 256AV (in a toshiba tecra 8000)
to display on the external vga.
I'm having mixed results - the good thing is:
the results I get make me happy, but...
I am just wondering if it might be easy to become even more happy...
(to get the 'onderste uit de kan' as we say in dutch :-)

when I use 1024x768x16 I get good image on internal lcd
when I then toggle to external display, it is fine too.
(with 1024x768x8 internal is ok, but external not:
 it displays a bit too much (some 'noise' appears 'outside'
 the normal rio background) and it is relatively dark,
 with thin more bright lines between the characters on the screen)

so, with 1024x768x16 I'm essentially happy, except:
still in 1024x768x16 mode on external vga:
when I now toggle to both (external + internal), it stops being nice:
top half of the screen gets a 'white overlay',
when I play more, it changes once more and it looks like the
size is somehow wrong, because pieces that belong next to each other
(e.g. the lines/pixels of the b3 menu) get drawn far away from each other.


essentially I'm just curious, and hoping:
does this sound like a 'known problem', with a 'standard' fix?
(if not, I'll just continue to be happy and avoid toggling between
 display modes too much)

I did find special, disabled, code for this chip in /sys/src/cmd/aux/vga.
Enabling it did make a difference in 1024x768x8 mode but was not perfect.

Axel.


             reply	other threads:[~2005-10-10 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-10 18:48 Axel Belinfante [this message]
2005-10-10 19:48 ` LiteStar numnums

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=200510101848.j9AImMC09095@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /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).