From: Antonino Daplas <adaplas@pol.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
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: Framebuffer fixes.
Date: 28 Mar 2003 04:49:34 +0800 [thread overview]
Message-ID: <1048798158.1035.13.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.21.0303272148280.7286-100000@vervain.sonytel.be>
On Fri, 2003-03-28 at 04:49, Geert Uytterhoeven wrote:
> > >
> > > Shouldn't these be info->var.bits_per_pixel instead of fb_logo.depth?
> >
> > Yes, fb_logo.depth == info->var.bits_per_pixel.
>
> Euh, now I get confused... Do you mean
> `Yes, it should be replaced by info->var.bits_per_pixel' or
> `No, logo.depth is always equal to info->var.bits_per_pixel'?
:) Sorry about that. I meant:
`No, fb_logo.depth is always equal to info->var.bits_per_pixel'
Tony
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-03-27 21:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 19:57 Framebuffer fixes James Simmons
2003-03-27 3:01 ` Antonino Daplas
2003-03-27 9:09 ` Geert Uytterhoeven
2003-03-27 19:15 ` Antonino Daplas
2003-03-27 20:49 ` Geert Uytterhoeven
2003-03-27 20:49 ` Antonino Daplas [this message]
2003-03-28 4:48 ` James Simmons
2003-03-28 8:00 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2003-03-28 11:02 ` Antonino Daplas
2003-03-28 13:18 ` Why moving driver includes ? Benjamin Herrenschmidt
2003-04-02 22:56 ` James Simmons
2003-03-27 20:43 ` Framebuffer fixes Antonino Daplas
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=1048798158.1035.13.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=geert@linux-m68k.org \
--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).