linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: David Eger <eger@havoc.gtf.org>, adaplas@pol.net
Cc: James Simmons <jsimmons@infradead.org>,
	Andrew Morton <akpm@osdl.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH][RIVAFB]: Updates to rivafb driver
Date: Thu, 17 Jun 2004 06:29:09 +0800	[thread overview]
Message-ID: <200406170629.09691.adaplas@hotpop.com> (raw)
In-Reply-To: <20040616173429.GA8601@havoc.gtf.org>

On Thursday 17 June 2004 01:34, David Eger wrote:
> On Wed, Jun 16, 2004 at 01:53:51PM +0800, Antonino A. Daplas wrote:
> > > On Wednesday 16 June 2004 06:17, David Eger wrote:
> > > > hey tony,
> > > >
> > > > your patch against drivers/video/riva/fbdev.c chokes on hunk 2 when
> > > > applied to 2.6.7-rc3-mm2.  resend, and i'll test it on my TNT2 :)
> > >
> > > Ok.  Patch against 2.6.7-rc3-mm2.
>
> Applying your rivafb and fbmode patches work great on my TNT2.
> I get a console with 160 columns and 60 rows :-)

That's great.

>
> And yes, the capabilities patch makes your driver slow.
> But setting the proper flags makes it fast again ;-)

Do you mind submitting a patch yourself?  It's probably a 1 liner patch, unless
we also modify rivafb to use cfb_* drawing functions depending on
the setting of var->accel_flags.

>
> The driver still doesn't play nice with the evil binary nvidia drivers,
> but then, that's expected.  (It'd be nice if changing from X to a console
> didn't *crash my machine* though.)
>

Yeah, even with XOrg/Free86 nv driver, it hangs.  Don't really know the exact
solution, probably a complete re-initialization of the hardware when switching from
X.  But this will require that fbcon recognizes a switch from X itself which it
currently doesn't (unless I'm mistaken).

Tony




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND

  reply	other threads:[~2004-06-16 22:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15 20:06 [PATCH][RIVAFB]: Updates to rivafb driver Antonino A. Daplas
2004-06-15 22:17 ` David Eger
2004-06-15 22:18   ` jsimmons
2004-06-16  2:44   ` Antonino A. Daplas
2004-06-16  5:53     ` Antonino A. Daplas
2004-06-16 16:47       ` jsimmons
2004-06-16 20:23         ` Andrew Morton
2004-06-16 22:29           ` Antonino A. Daplas
2004-06-16 22:39             ` Andrew Morton
2004-06-17 18:24             ` [PATCH][RIVAFB] rivafb: fb accel capabilities David Eger
2004-06-16 17:34       ` [PATCH][RIVAFB]: Updates to rivafb driver David Eger
2004-06-16 22:29         ` Antonino A. Daplas [this message]
2004-06-17  0:16           ` David Eger
2004-06-17 16:34             ` Benjamin Herrenschmidt

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=200406170629.09691.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=eger@havoc.gtf.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).