From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] NeoMagic MagicGraph 128 (NM2070, 10c8/0001)
Date: Sat, 8 Jan 2005 18:52:30 -0500 [thread overview]
Message-ID: <a461e960a83e5c03729a8740f67bc3a9@plan9.bell-labs.com> (raw)
In-Reply-To: <16311.1105224958@piper.nectar.cs.cmu.edu>
Looking at the XFree86 code (which is is the only documentation
available, I believe), you see the 2070 is the odd man out, requiring
extra fiddling. I suspect that whoever did the original code thought
it wasn't worth the effort for what looks like the oldest chip
especially if there was no hardware on hand to test it on.
It's probably not hard to add, start with
.../xc/programs/Xserver/hw/xfree86/drivers/neomagic/neo_driver.c
and just step through it looking for the string "2070" and comparing
what's there to what's in /sys/src/cmd/aux/vga/neomagic.c and
/sys/src/9/pc/vganeomagic.c. It looks like you may have to alter
the latter of those for acceleration.
--jim
On Sat Jan 8 17:57:01 EST 2005, davide+p9@cs.cmu.edu wrote:
> vgadb and aux/vga explicitly rejects this chip as unsupported.
>
> Sure enough, if add the "appropriate" case statements there and
> in the kernel I get a screen full of hash.
>
> Any hints on what's wrong? Does whoever declared the chip
> unsupported remember whether there was a known problem which
> was the obstacle, or just a lack of debugging cycles?
>
> Dave Eckhardt
next prev parent reply other threads:[~2005-01-08 23:52 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 [this message]
2005-01-17 13:11 ` Dave Eckhardt
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=a461e960a83e5c03729a8740f67bc3a9@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--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).