From: Sven Luther <sven.luther@wanadoo.fr>
To: Clint Adams <schizo@debian.org>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
226973@bugs.debian.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Bug#226973: xserver-xfree86: [glint] second card at wrong resolution
Date: Wed, 14 Jan 2004 22:12:13 +0100 [thread overview]
Message-ID: <20040114211213.GB6573@iliana> (raw)
In-Reply-To: <20040114210635.GA31286@scowler.net>
On Wed, Jan 14, 2004 at 04:06:35PM -0500, Clint Adams wrote:
> > Yep. It probably doesn't happen on x86, since the int10 stuff
> > initializes the card with the onboard bios. Using a x86 emulator in X to
> > run this bios might be a solution.
>
> According to Tech-Source, this card has no VGA bios..
Ok. An OF driver then ?
> > Ho. definitively some registers who are bad. It has been a long time
> > since i have looked at the pm2 specs (kind of 98ish i think) though.
> > Maybe you could get hand of the free TI-pm2 specs and look for yourself ?
>
> I've been looking and not finding anything.
you did not find the specs, or you didn't find anything ?
> > You would dump all the possible registers, and see which one is
> > different. Enabling debugging in the glint driver would also do. You can
> > safely run no-accel on these for the tests, as this is definitively not
> > an accel issue, but a video out/ramdac one.
>
> Attached is the XFree86.0.log from xserver-xfree86-dbg. I'll start it
> again with noaccel. The only thing I notice is that it thinks the
> second card only has 4 megs of video ram.
Nope, this is not the right way, you have to rebuild the driver and add
some code to drop the content of the registers somewhere.
I don't have time right now, maybe later i will find time to send you a
register dropping patch or something.
Friendly,
Sven Luther
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
next prev parent reply other threads:[~2004-01-14 21:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040109163119.GA10151@scowler.net>
[not found] ` <20040112121558.GA24511@iliana>
[not found] ` <20040112215543.GB2150@scowler.net>
2004-01-13 7:41 ` Bug#226973: xserver-xfree86: [glint] second card at wrong resolution Sven Luther
2004-01-13 15:40 ` Clint Adams
2004-01-13 16:02 ` Sven Luther
2004-01-14 21:06 ` Clint Adams
2004-01-14 21:12 ` Sven Luther [this message]
2004-01-14 21:17 ` Clint Adams
2004-01-14 21:12 ` Clint Adams
2004-01-14 21:16 ` Sven Luther
2004-01-15 21:55 ` Clint Adams
2004-01-15 22:47 ` Clint Adams
2004-03-30 15:32 ` Clint Adams
2004-03-30 16:57 ` Sven Luther
2004-03-30 23:02 ` Clint Adams
2004-03-30 23:08 ` Sven Luther
2004-03-31 8:12 ` Geert Uytterhoeven
2004-03-31 16:10 ` Clint Adams
2004-04-01 6:41 ` Bug#226973: " Branden Robinson
2004-04-01 6:51 ` Sven Luther
2004-04-01 16:41 ` Branden Robinson
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=20040114211213.GB6573@iliana \
--to=sven.luther@wanadoo.fr \
--cc=226973@bugs.debian.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=schizo@debian.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).