> > No, bits_per_pixel can be (much) larger than the color map size. E.g. a
> > simple
> > ARGB 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.
> > 3) Add another file in sysfs which specifies at what index and how many
> > entries will be read or written from or to the cmap. With this additional
> > sysfs file, it should be able to handle any reasonable cmap length, but
> > it will take more than one reading of the color_map file. Anot
On 7/29/05, Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
> On Fri, 29 Jul 2005, Antonino A. Daplas wrote:
> > Jon Smirl wrote:
> > > On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
> > > > On Thu, 28 Jul 2005, Jon Smirl wrote:
> > > > > I've verified now that all ATI R300+ chips have 10b
On Fri, 29 Jul 2005, Antonino A. Daplas wrote:
> Jon Smirl wrote:
> > On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> 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 maki
Geert Uytterhoeven wrote:
On Thu, 28 Jul 2005, Antonino A. Daplas wrote:
Jon Smirl wrote:
On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
On Wed, 27 Jul 2005, Linux Kernel Mailing List wrote:
There are a couple of ways to fix this.
1) Add a check to limit use of the sysfs attributes
Jon Smirl wrote:
On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> 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
Jon Smirl wrote:
Can you review this fix for the issues below? I fixed things to
automatically adjust the number of entries to whatever fits in
PAGE_SIZE.
diff --git a/drivers/video/fbsysfs.c b/drivers/video/fbsysfs.c
--- a/drivers/video/fbsysfs.c
+++ b/drivers/video/fbsysfs.c
@@ -244,15 +244,15
On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> 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. G
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 tabl
On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> 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 suppo
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 en
On 7/28/05, Jon Smirl <[EMAIL PROTECTED]> wrote:
> On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> 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
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?
> I wouldn't even be messing with cmap except for the true/direct color
> support and gamma ramps. Don't I need to
I can't see a way to query how long of cmap the device supports using
the current fbdev ioctls.
I wouldn't even be messing with cmap except for the true/direct color
support and gamma ramps. Don't I need to know how long the cmap is in
order to set the right gamma ramp?
If I set a 256 entry gamma
On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
> On Thu, 28 Jul 2005, Antonino A. Daplas wrote:
> > Jon Smirl wrote:
> > > On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
> > > > On Wed, 27 Jul 2005, Linux Kernel Mailing List wrote:
> > >
> > > There are a couple of ways to fix
On Thu, 28 Jul 2005, Antonino A. Daplas wrote:
> Jon Smirl wrote:
> > On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
> > > On Wed, 27 Jul 2005, Linux Kernel Mailing List wrote:
> >
> > There are a couple of ways to fix this.
> > 1) Add a check to limit use of the sysfs attributes to 25
Jon Smirl wrote:
On 7/28/05, Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
On Wed, 27 Jul 2005, Linux Kernel Mailing List wrote:
There are a couple of ways to fix this.
1) Add a check to limit use of the sysfs attributes to 256 entries. If
you want more you have to use /dev/fb0 and the ioct
17 matches
Mail list logo
