From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] NeoMagic MagicGraph 128 (NM2070, 10c8/0001)
Date: Mon, 17 Jan 2005 08:11:18 -0500 [thread overview]
Message-ID: <14559.1105967478@piper.nectar.cs.cmu.edu> (raw)
In-Reply-To: <a461e960a83e5c03729a8740f67bc3a9@plan9.bell-labs.com>
Based on Jim's advice, I've been working on extending the neomagic
driver to support the primeval NM2070. I've made a bunch of progress
but would appreciate some informed advice.
The good news so far is:
* kernel code restructured to deal with 2070's single PCI memory region
* timing problems specific to 2070 fixed by ramming undocumented constants
into "shadow registers" the way XF86 does
* existing cursor code correctly draws and positions
* rio paints grey desktop background
* the BIOS battery-status icon paints & unpaints when requested
For the moment I disabled acceleration (by not filling in scr->fill or
scr->scroll) since the 2070 doesn't do that the same way as later chips.
Current bad news:
* there is a band of bad pixels near the bottom of the screen which looks
sort of like a random-dot stereogram
* when I right-button to bring up the rio menu, parts of it appear scattered
to the right and below the correct place (30-ish little scraps, each fairly
recognizable). When the menu pops down, the scattered parts are un-drawn
and the desktop is gray again.
Does the latter look like any standard mistake to anybody, e.g., "you're
not really in linear mode", "there is a scanline padding problem", etc.?
Is it possible that the memory layout is weird in some way which requires
acceleration for the chip to work? If that seems likely I can push on that
for a while.
Dave Eckhardt
prev parent reply other threads:[~2005-01-17 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 22:55 Dave Eckhardt
2005-01-08 23:52 ` jmk
2005-01-17 13:11 ` Dave Eckhardt [this message]
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=14559.1105967478@piper.nectar.cs.cmu.edu \
--to=davide+p9@cs.cmu.edu \
--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).