public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Linux Fbdev development list 
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tdfx ported to new fbdev api
Date: Thu, 28 Feb 2002 22:11:52 +0100	[thread overview]
Message-ID: <20020228221152.K32662@suse.de> (raw)
In-Reply-To: <20020228214045.E32662@suse.de> <Pine.LNX.4.10.10202281242570.20040-100000@www.transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10202281242570.20040-100000@www.transvirtual.com>; from jsimmons@transvirtual.com on Thu, Feb 28, 2002 at 12:44:26PM -0800

On Thu, Feb 28, 2002 at 12:44:26PM -0800, James Simmons wrote:
 > Their are a few changes. I tested it last night and it worked for me. That
 > doesn't mean much so if you could give it a try. BTW the penguin will not
 > show up. I need to expand the imageblit function but it is not top
 > priority right now.

 Now that you mention the penguin, I was reminded of something.
 Normally with this box, when the fb starts, the top 3rd of the
 screen has a large white rectangle blitted onto it for reasons
 I never figured out. Its purely cosmetic (it disappears when scrolling
 begins), so it wasn't something I really bothered investigating.

 It could be that with your reworking, this bug has taken on
 a new form, and is now doing something more dramatic.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-02-28 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 16:22 [PATCH] tdfx ported to new fbdev api James Simmons
2002-02-28 20:40 ` Dave Jones
2002-02-28 20:44   ` James Simmons
2002-02-28 21:11     ` Dave Jones [this message]
2002-03-01  2:24       ` Joseph Fannin
2002-02-28 21:00   ` [Linux-fbdev-devel] " James Simmons
2002-02-28 21:08     ` Dave Jones
2002-03-01  7:19       ` Jurriaan on Alpha

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=20020228221152.K32662@suse.de \
    --to=davej@suse.de \
    --cc=jsimmons@transvirtual.com \
    --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