All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@gmail.com>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH] fbdev: colormap fixes
Date: Fri, 29 Jul 2005 06:34:20 -0400	[thread overview]
Message-ID: <9e47339105072903345cb37164@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0507290942080.5163@numbat.sonytel.be>

On 7/29/05, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Fri, 29 Jul 2005, Antonino A. Daplas wrote:
> > Jon Smirl wrote:
> > > On 7/28/05, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > > > On Thu, 28 Jul 2005, Jon Smirl wrote:
> > > > > I've verified now that all ATI R300+ chips have 10bit cmaps. These are
> > > > > pretty common so I'd be in favor of making this into a binary
> > > > > attribute where I can get/set the whole table at once. Given that
> > > > > OpenGL is already supporting 12 and 16 bits these tables are only
> > > > > going to get much larger.
> > > > >
> > > > > 1024 entries * 5 fields * 2 bytes = 10KB -- too big for a text
> > > > > attribute.
> > > > >
> > > > > 65536 entries * 5 fields * 2 bytes = 655KB -- way too big for a text
> > > > > attribute.
> > > > >
> > > > > The bits_per_pixel sysfs attribute is an easy way to tell how many
> > > > > entries you need. You can just set it at 4, 8, 10, etc until you get
> > > > > an error. Now you know the max. 2^n and you know how many entries.
> > > > No, bits_per_pixel can be (much) larger than the color map size. E.g. a
> > > > simple
> > > > ARGB8888 directcolor mode has bits_per_pixel = 32 and color map size =
> > > > 256.
> > >
> > > So I have the bits_per_pixel attribute wrong in sysfs. It needs to be
> > > bits_per_color and then let the driver sort it out.  Otherwise there
> > > is no way to set ARGB8888 versus ARGB2101010. With bits per color you
> > > would set 8 or 10.
> >
> > No, you have to add another attribute for {transp|red|green|blue}.{len,offset}
> > and another attribute for the pixelformat. Then using those, one can
> > easily deduce the cmap size.
> 
> Indeed. One bits_per_color cannot handle e.g. RGB565 (or RGBA{10,10,10,2} :-).
> 
> > > If that isn't good enough I can switch the attribute to take strings
> > > like ARGB8888.
> > >
> >
> > Please no.
> 
> Ack.

> 
> > > What do you think, should I just switch to fbconfig names and a binary
> > > cmap attribute?
> >
> > Does a binary attribute not have the same buffer size limitation as
> > the text attribute?  I really don't know, just asking.
> 
> Yes it has, but since binary data is more compact, you can fit more data in
> PAGE_SIZE.

Binary attributes are not limited to page size.

-- 
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: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@gmail.com>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: [PATCH] fbdev: colormap fixes
Date: Fri, 29 Jul 2005 06:34:20 -0400	[thread overview]
Message-ID: <9e47339105072903345cb37164@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0507290942080.5163@numbat.sonytel.be>

On 7/29/05, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Fri, 29 Jul 2005, Antonino A. Daplas wrote:
> > Jon Smirl wrote:
> > > On 7/28/05, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > > > On Thu, 28 Jul 2005, Jon Smirl wrote:
> > > > > I've verified now that all ATI R300+ chips have 10bit cmaps. These are
> > > > > pretty common so I'd be in favor of making this into a binary
> > > > > attribute where I can get/set the whole table at once. Given that
> > > > > OpenGL is already supporting 12 and 16 bits these tables are only
> > > > > going to get much larger.
> > > > >
> > > > > 1024 entries * 5 fields * 2 bytes = 10KB -- too big for a text
> > > > > attribute.
> > > > >
> > > > > 65536 entries * 5 fields * 2 bytes = 655KB -- way too big for a text
> > > > > attribute.
> > > > >
> > > > > The bits_per_pixel sysfs attribute is an easy way to tell how many
> > > > > entries you need. You can just set it at 4, 8, 10, etc until you get
> > > > > an error. Now you know the max. 2^n and you know how many entries.
> > > > No, bits_per_pixel can be (much) larger than the color map size. E.g. a
> > > > simple
> > > > ARGB8888 directcolor mode has bits_per_pixel = 32 and color map size =
> > > > 256.
> > >
> > > So I have the bits_per_pixel attribute wrong in sysfs. It needs to be
> > > bits_per_color and then let the driver sort it out.  Otherwise there
> > > is no way to set ARGB8888 versus ARGB2101010. With bits per color you
> > > would set 8 or 10.
> >
> > No, you have to add another attribute for {transp|red|green|blue}.{len,offset}
> > and another attribute for the pixelformat. Then using those, one can
> > easily deduce the cmap size.
> 
> Indeed. One bits_per_color cannot handle e.g. RGB565 (or RGBA{10,10,10,2} :-).
> 
> > > If that isn't good enough I can switch the attribute to take strings
> > > like ARGB8888.
> > >
> >
> > Please no.
> 
> Ack.

> 
> > > What do you think, should I just switch to fbconfig names and a binary
> > > cmap attribute?
> >
> > Does a binary attribute not have the same buffer size limitation as
> > the text attribute?  I really don't know, just asking.
> 
> Yes it has, but since binary data is more compact, you can fit more data in
> PAGE_SIZE.

Binary attributes are not limited to page size.

-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2005-07-29 10:34 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
2005-07-28 20:15                 ` [Linux-fbdev-devel] " 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 [this message]
2005-07-29 10:34                               ` 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=9e47339105072903345cb37164@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@gmail.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 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.