From: Antonino Daplas <adaplas@pol.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Fredrik Noring <noring@nocrew.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Interlace for rivafb driver
Date: 30 Jan 2003 10:35:33 +0800 [thread overview]
Message-ID: <1043893542.1052.130.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0301281927590.12076-100000@phoenix.infradead.org>
On Wed, 2003-01-29 at 03:29, James Simmons wrote:
> On 26 Jan 2003, Fredrik Noring wrote:
>
> > Attached patch implements interlace for the rivafb driver and
> > the hardware that supports it (Riva 128, TNT, TNT2, some GeForce
> > cards and possibly others).
> >
> > It's a patch against 2.4.21-pre2 (with polarity and sync patches)
> > but it should fit with 2.5.x too skipping riva_hw.c and riva_hw.h
> > which already are adopted from XFree86.
>
> Applied.
>
>
> P.S
> To Tony. I applied your patches as well. The only patch I didn't was
> the DIRECTCOLOR patch. The X server freaked out for my card when the video
> mode was in a DIRECTCOLOR state.
>
Yes I'm not sure about this too. Also the patch I submitted is untested
for RGB565, tested only for RGB555 and RGB8888. So, does X work for
rivafb? It does not work in my hardware unless I add the directcolor
patch.
Tony
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-01-30 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 23:08 [PATCH] Interlace for rivafb driver Fredrik Noring
2003-01-28 19:29 ` James Simmons
2003-01-30 2:35 ` Antonino Daplas [this message]
2003-01-30 19:34 ` James Simmons
2003-01-30 22:59 ` Antonino Daplas
2003-02-12 20:09 ` 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=1043893542.1052.130.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=noring@nocrew.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).