All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Antonino A. Daplas" <adaplas@gmail.com>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH] fbdev: colormap fixes
Date: Thu, 28 Jul 2005 16:15:40 -0400	[thread overview]
Message-ID: <9e4733910507281315419c3c12@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0507282202450.29876@numbat.sonytel.be>

On 7/28/05, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Thu, 28 Jul 2005, Jon Smirl wrote:
> > I can't see a way to query how long of cmap the device supports using
> > the current fbdev ioctls.
> 
> Look at the lengths of the color bitfields?

Which color bitfields? Does hardware that supports 10bit cmap also
support a 10:10:10 framebuffer? If you can't do 10:10:10 how do the
10bit cmaps work?  Does alpha matter in a 10:10:10 scanout buffer?

-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

WARNING: multiple messages have this Message-ID (diff)
From: Jon Smirl <jonsmirl@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Antonino A. Daplas" <adaplas@gmail.com>,
	Linux Frame Buffer Device Development 
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: [PATCH] fbdev: colormap fixes
Date: Thu, 28 Jul 2005 16:15:40 -0400	[thread overview]
Message-ID: <9e4733910507281315419c3c12@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0507282202450.29876@numbat.sonytel.be>

On 7/28/05, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Thu, 28 Jul 2005, Jon Smirl wrote:
> > I can't see a way to query how long of cmap the device supports using
> > the current fbdev ioctls.
> 
> Look at the lengths of the color bitfields?

Which color bitfields? Does hardware that supports 10bit cmap also
support a 10:10:10 framebuffer? If you can't do 10:10:10 how do the
10bit cmaps work?  Does alpha matter in a 10:10:10 scanout buffer?

-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2005-07-28 20:15 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200507280031.j6S0V3L3016861@hera.kernel.org>
2005-07-28  7:54 ` [PATCH] fbdev: colormap fixes Geert Uytterhoeven
2005-07-28  7:54   ` Geert Uytterhoeven
2005-07-28 13:07   ` Jon Smirl
2005-07-28 13:07     ` Jon Smirl
2005-07-28 13:40     ` Geert Uytterhoeven
2005-07-28 13:40       ` Geert Uytterhoeven
2005-07-28 14:50     ` Antonino A. Daplas
2005-07-28 14:50       ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-07-28 15:59       ` Geert Uytterhoeven
2005-07-28 15:59         ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-07-28 16:29         ` Jon Smirl
2005-07-28 16:29           ` [Linux-fbdev-devel] " Jon Smirl
2005-07-28 18:18           ` Jon Smirl
2005-07-28 18:18             ` [Linux-fbdev-devel] " Jon Smirl
2005-07-28 20:03             ` Geert Uytterhoeven
2005-07-28 20:03               ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-07-28 20:15               ` Jon Smirl [this message]
2005-07-28 20:15                 ` Jon Smirl
2005-07-28 20:21                 ` Jon Smirl
2005-07-28 20:21                   ` [Linux-fbdev-devel] " Jon Smirl
2005-07-28 20:50                   ` Jon Smirl
2005-07-28 20:50                     ` [Linux-fbdev-devel] " Jon Smirl
2005-07-28 21:39                     ` Geert Uytterhoeven
2005-07-28 21:39                       ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-07-28 21:50                       ` Jon Smirl
2005-07-28 21:50                         ` [Linux-fbdev-devel] " Jon Smirl
2005-07-28 22:28                         ` Antonino A. Daplas
2005-07-28 22:28                           ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-07-29  7:43                           ` Geert Uytterhoeven
2005-07-29  7:43                             ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-07-29 10:34                             ` Jon Smirl
2005-07-29 10:34                               ` [Linux-fbdev-devel] " Jon Smirl
2005-07-29 20:20                         ` James Simmons
2005-07-29 20:20                           ` [Linux-fbdev-devel] " James Simmons
2005-07-28 23:19         ` Antonino A. Daplas
2005-07-28 23:19           ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-07-29 20:13         ` James Simmons
2005-07-29 20:13           ` [Linux-fbdev-devel] " James Simmons
2005-07-28 14:45   ` Jon Smirl
2005-07-28 14:45     ` Jon Smirl
2005-07-28 15:56     ` Geert Uytterhoeven
2005-07-28 15:56       ` Geert Uytterhoeven
2005-07-28 19:31     ` Jon Smirl
2005-07-28 19:31       ` Jon Smirl
2005-07-28 20:04       ` Geert Uytterhoeven
2005-07-28 20:04         ` Geert Uytterhoeven
2005-07-28 22:16     ` Antonino A. Daplas
2005-07-28 22:16       ` [Linux-fbdev-devel] " Antonino A. 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=9e4733910507281315419c3c12@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@gmail.com \
    --cc=geert@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.