linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Antonino Daplas <adaplas@pol.net>
Cc: James Simmons <jsimmons@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Much better framebuffer fixes.
Date: Thu, 27 Mar 2003 10:33:52 +0100	[thread overview]
Message-ID: <3E82C580.1000801@aitel.hist.no> (raw)
In-Reply-To: 1048735712.1047.10.camel@localhost.localdomain

Antonino Daplas wrote:
> On Thu, 2003-03-27 at 08:18, James Simmons wrote:
> 
>>Okay. Here are more framebuffer fixes. Please try these fixes and let me 
>>know how they work out for you.
>>
> 
> 
> This is a resend of the patch I previously sent.  I see that you have
> made changes to the logo drawing code targeted for monochrome logo
> drawing to use mono expansion.  You still need a few changes though,
> image->bg_color and image->fg_color must be initialized correctly when
> image->depth == 1.

This applied on top of James Simmons' patch, but didn't compile.
spin_lock_irqsave was "unknown".


Helge Hafting



-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en

  reply	other threads:[~2003-03-27  9:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27  0:18 Much better framebuffer fixes James Simmons
2003-03-27  3:29 ` [Linux-fbdev-devel] " Antonino Daplas
2003-03-27  9:33   ` Helge Hafting [this message]
2003-03-27 17:16     ` Thomas Schlichter
2003-03-27 19:15       ` Antonino Daplas
2003-03-27  9:18 ` Geert Uytterhoeven
2003-03-27 19:15   ` Antonino Daplas
2003-03-27  9:58 ` Helge Hafting
2003-03-27 15:58   ` Thomas Molina

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=3E82C580.1000801@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=adaplas@pol.net \
    --cc=jsimmons@infradead.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).