From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Ani Joshi <ajoshi@shell.unixbox.com>, William Blew <wblew@home.com>
Cc: michel dnzer <michdaen@iiic.ethz.ch>,
kaoru fukui <k_fukui@highway.ne.jp>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: XF4 (mach64) help please
Date: Thu, 19 Apr 2001 19:21:51 +0100 [thread overview]
Message-ID: <20010419182214.BF2DE2EFCB@apollo.valhalla.net> (raw)
On Thu, Apr 19, 2001, Ani Joshi wrote:
> On Thu, 19 Apr 2001, William Blew wrote:
>
>> On Thu, 19 Apr 2001, Iain Sandoe wrote:
>>
>> > 2/ how difficult would it be to plumb the scroll acceleration back into
the
>> > console driver? (would one need access to the NDA stuff?) -- the scrolling
>> > of console is a real problem in blocking sound :-/
>>
>> For mach64 at least, I would start by porting the CopyScreen2Screen XXA
>> operation into the kernel and then using it during scrolling.
>
> This is already done by atyfb in the kernel,
then why is the atyfb scroll (and fbdevhw) _so_ much slower than the X
'native' driver ... the same reason as below?
>however the problem lies in
> the entire fbcon layer where there is some improper locking/interrupts
> going on there. This was discussed here and on linux-fbdev a few months
> ago and I believe will be addressed in 2.5.
and there is a (temporary) fix for it (I believe) involving a patch from
Andrew Morton - (which I haven't had time to try on PPC yet). Will that fix
the slow console scroll as well?
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-04-19 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 18:21 Iain Sandoe [this message]
2001-04-19 18:38 ` XF4 (mach64) help please Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 19:07 Iain Sandoe
2001-04-19 12:36 Iain Sandoe
2001-04-19 15:46 ` William Blew
2001-04-19 17:57 ` Ani Joshi
2001-04-16 15:15 Iain Sandoe
2001-04-16 21:47 ` Michel Dänzer
2001-04-17 4:07 ` Ani Joshi
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=20010419182214.BF2DE2EFCB@apollo.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=ajoshi@shell.unixbox.com \
--cc=k_fukui@highway.ne.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michdaen@iiic.ethz.ch \
--cc=wblew@home.com \
/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).