From: James Simmons <jsimmons@infradead.org>
To: Ben Collins <bcollins@debian.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [FBDEV UPDATE] Newer patch.
Date: Thu, 30 Oct 2003 18:38:46 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.44.0310301833140.4560-100000@phoenix.infradead.org> (raw)
In-Reply-To: <20031023234552.GB554@phunnypharm.org>
> I noticed one thing, and that is that the mach64 used to use software
> cursor it seems (I remember wondering why atyfb_cursor was never used
> anywhere). It's now using the hw cursor.
Yeap. I'm in the process of getting several driver to use there hardware
cursors.
> Also, I notice with this new code that the random vertical shifting of
> the console doesn't occur anymore like it does with current 2.6.0-test8
> code. For as long as I can remember 2.6.0-test, and way back into
> 2.5.5x, this has been a problem with highly active console programs
> (mutt, vim, etc...). Good to see it's going away :)
:-)
I have fixed the problems you have reported. I have a newer patch. Note
this is updated with the LCD support. I like to see if the patch works on
sparc. I has updates from the latest 2.4.X kernels. Please give it a try.
http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
Let me know the results.
next prev parent reply other threads:[~2003-10-30 18:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 17:31 [FBDEV UPDATE] Newer patch James Simmons
2003-10-22 20:38 ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-10-22 21:46 ` James Simmons
2003-10-22 20:50 ` jhf
2003-10-22 21:46 ` James Simmons
2003-10-23 10:00 ` Geert Uytterhoeven
2003-10-23 14:43 ` Ben Collins
2003-10-23 22:50 ` James Simmons
2003-10-23 23:45 ` Ben Collins
2003-10-30 18:38 ` James Simmons [this message]
2003-10-30 23:07 ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-11-17 18:38 ` Ben Collins
[not found] <E1AFJKq-0000Lb-7o@rhn.tartu-labor>
2003-11-03 14:36 ` Meelis Roos
2003-11-03 14:41 ` Meelis Roos
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=Pine.LNX.4.44.0310301833140.4560-100000@phoenix.infradead.org \
--to=jsimmons@infradead.org \
--cc=bcollins@debian.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).