From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: James Simmons <jsimmons@infradead.org>
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
Jurriaan <thunder7@xs4all.nl>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.65 + matrox framebuffer: life is good!
Date: Tue, 25 Mar 2003 19:35:24 +0100 [thread overview]
Message-ID: <74B3EA2366@vcnet.vc.cvut.cz> (raw)
On 25 Mar 03 at 18:16, James Simmons wrote:
> > > Its for testing and it hasn't been fully ported over yet. Its close.
> > > I was busy fixing higher level bugs but now that most are fixed I can work
> > > on the matrox driver again.
> >
> > There are still some open problems (text mode, hardware cursor), and I missed
> > something somewhere, as czech font works only on VT1 console with mga-2.5.65
> > (on other VTs there is some font loaded, but character mapping looks broken).
> > I have no idea whether it is my problem or James's...
>
> I have tested font changing. It works.
I'll have to look into my changes then :-(
> > Probably worst problem currently is cursor code: it calls imgblit from interrupt
> > context, and matroxfb's accelerated procedures are not ready to handle
> > such thing (patch hooks cursor call much sooner for primary mga head).
>
> Fixed now. Also I have a patch that properly fixes image.depth = 0 hack. I
> will post for people to test. Folks please test the code.
AFAIK you only fixed kmalloc problem. Or is cursor callback disallowed
while doing imgblit/copyarea/fillrect ?
Petr Vandrovec
next reply other threads:[~2003-03-25 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 18:35 Petr Vandrovec [this message]
2003-03-25 20:48 ` 2.6.65 + matrox framebuffer: life is good! James Simmons
-- strict thread matches above, loose matches on Subject: below --
2003-03-25 21:28 Petr Vandrovec
2003-03-21 18:43 Jurriaan
2003-03-23 12:09 ` Helge Hafting
2003-03-23 16:50 ` James Simmons
2003-03-24 8:39 ` Petr Vandrovec
2003-03-25 18:16 ` James Simmons
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=74B3EA2366@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=helgehaf@aitel.hist.no \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/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