From: anthony tong <atong@uiuc.edu>
To: Charlie McLachlan <cim@uk.research.att.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Accel ATI Rage 128 support, the very first step (Help needed)
Date: Thu, 28 Oct 1999 01:25:52 -0500 [thread overview]
Message-ID: <19991028012551.A16581@mango.genunix.net> (raw)
In-Reply-To: <Pine.SO4.4.04.9910271119020.5658-100000@marrow>
Charlie McLachlan (Wed, Oct 27, 1999 at 11:46:15AM +0100):
> The result was that vertical scolling worked fine (i.e. when you typed
> to the bottom of the screen the scroll upward was okay) but when scrooling
> horizontally (like when you back cursor through a line then add more
> characters) the remains of the line (the bit to the right of the cursor)
> is not moved.
this might be a shell vs. termcap/terminfo problem.
> 1) What gives? Why isn't bmove (seemingly) used for vertical console
> scrolls?
Because it's slow. If you want to try it set display->scrollmode to 0.
Be warned though it's not really ready for prime time use (you need
to make sure that the engine isn't busy).. simple stuff but I simply
didn't have the time to sit down and test it.
> 2) If I recompile aty128fb, how do I replace the currently active version
> without having to restart? (i.e. how do I change frame buffer modules?)
You don't; at least, I've never been able to unregister a fbdev driver
and re-registering a new one. I'm not sure if this has been fixed recently
though.
> 3) Have I got this all wrong? Is bmove even what I should be thinking of?
I'd look into panning + getting a rectfill. I'll try and do it this
weekend if I have the time.
> 5) Antony's code references registers through info->regbase (which is a
> big long hex number with some 8's in it). The Suse code references
> registers through (PCIDevice->_basel & 0xffffff00), where PCIDevice is a
> pciconfigPtr found through probing. Is this the same thing?
Pretty much.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-28 6:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-20 19:43 SuSE Rage 128 Xserver Source and XFree 3.3.6 Kevin B. Hendricks
1999-10-20 20:05 ` anthony tong
1999-10-20 23:23 ` Kevin B. Hendricks
1999-10-20 23:25 ` Dan Burcaw
1999-10-27 10:46 ` Accel ATI Rage 128 support, the very first step (Help needed) Charlie McLachlan
1999-10-27 18:26 ` Ryuichi Oikawa
1999-10-28 7:40 ` Accel ATI Rage 128 support, (another test Xserver) anthony tong
1999-10-28 6:25 ` anthony tong [this message]
1999-10-28 18:44 ` Accel ATI Rage 128 support, the very first step (Help needed) Geert Uytterhoeven
1999-10-21 0:04 ` SuSE Rage 128 Xserver Source and XFree 3.3.6 anthony tong
1999-10-21 9:33 ` Charlie McLachlan
1999-10-21 10:44 ` Sven LUTHER
1999-10-21 19:42 ` anthony tong
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=19991028012551.A16581@mango.genunix.net \
--to=atong@uiuc.edu \
--cc=cim@uk.research.att.com \
--cc=linuxppc-dev@lists.linuxppc.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).