[directfb-users] Hello

[Chuck McManis]

Greetings everyone.

I'm really happy to have found DirectFB, I'm hoping it will help me to
achieve my goals of creating some intelligent digital signs.

I'm using a Pandaboard ES, which is running Ubunto 12.04.1 LTS with the TI
supplied OMAP drivers. I am not running X11 on this system and Wayland
isn't yet supported, but our old friend /dev/fb0 works fine :-)

I pulled a copy of DirectFB from git, built it natively using
--with-gfxdrivers=omap and it built and installed (woot!) and I can run
most of the demos (there are a few things that break from missing data
files but that is ok)

I would love it if I could get 2D acceleration, not sure if that is from
the omap driver or the pvr2d driver (which I did not build, but I could try
I suppose).

My first question is this one, when I run any dfb program (and dfbinfo as
well) I get this error:

(*) FBDev/Mode: Setting 1920x1080 RGB32
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit
(RGB32), pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument
(*) FBDev/Mode: Setting 1920x1080 RGB32
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit
(RGB32), pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument

This comes from the code in systems/fbdev.c where it has this :

D_INFO( "FBDev/Mode: Switched to %dx%d (virtual %dx%d) at %d bit (%s),
pitch %d\n",
var.xres, var.yres, var.xres_virtual, var.yres_virtual,
var.bits_per_pixel,
dfb_pixelformat_name(config->format), shared->fix.line_length
);

if (config->format == DSPF_RGB332)
dfb_fbdev_set_rgb332_palette();
else
dfb_fbdev_set_gamma_ramp( config->format );

This seems like it is trying to set a gamma ramp because the config->format
value isn't recognized as a truecolor format?

--Chuck

[haithem rahmani]

Hello,

have you tried the ARGB pixelformat?

$>dfbinfo --dfb:pixelformat=ARGB

regards
Haithem

Post by Chuck McManis
Greetings everyone.
I'm really happy to have found DirectFB, I'm hoping it will help me to
achieve my goals of creating some intelligent digital signs.
I'm using a Pandaboard ES, which is running Ubunto 12.04.1 LTS with the TI
supplied OMAP drivers. I am not running X11 on this system and Wayland
isn't yet supported, but our old friend /dev/fb0 works fine :-)
I pulled a copy of DirectFB from git, built it natively using
--with-gfxdrivers=omap and it built and installed (woot!) and I can run
most of the demos (there are a few things that break from missing data
files but that is ok)
I would love it if I could get 2D acceleration, not sure if that is from
the omap driver or the pvr2d driver (which I did not build, but I could try
I suppose).
My first question is this one, when I run any dfb program (and dfbinfo as
(*) FBDev/Mode: Setting 1920x1080 RGB32
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit
(RGB32), pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument
(*) FBDev/Mode: Setting 1920x1080 RGB32
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit
(RGB32), pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument
D_INFO( "FBDev/Mode: Switched to %dx%d (virtual %dx%d) at %d bit
(%s), pitch %d\n",
var.xres, var.yres, var.xres_virtual, var.yres_virtual,
var.bits_per_pixel,
dfb_pixelformat_name(config->format), shared->fix.line_length
);
if (config->format == DSPF_RGB332)
dfb_fbdev_set_rgb332_palette();
else
dfb_fbdev_set_gamma_ramp( config->format );
This seems like it is trying to set a gamma ramp because the
config->format value isn't recognized as a truecolor format?
--Chuck
_______________________________________________
directfb-users mailing list
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

[Chuck McManis]

On Sun, Aug 19, 2012 at 1:59 PM, haithem rahmani

Post by haithem rahmani
Hello,
have you tried the ARGB pixelformat?
$>dfbinfo --dfb:pixelformat=ARGB

Sadly same result:
(*) FBDev/Mode: Setting 1920x1080 ARGB
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit (ARGB),
pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument
(*) FBDev/Mode: Setting 1920x1080 ARGB
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit (ARGB),
pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument

The error comes from this call:

if (FBDEV_IOCTL( FBIOPUTCMAP, cmap ) < 0) {
D_PERROR( "DirectFB/FBDev: "
"Could not set gamma ramp" );

return errno2result(errno);
}

/proc/fb is '0 omapdrm' (which is to say the framebuffer is driven by the
omapdrm module) and apparently it chokes on the FBIOPUTCMAP ioctl. I'm
reaching out to the TI guys to see what they have to say as well.

--Chuck

Post by haithem rahmani
regards
Haithem

Post by Chuck McManis
Greetings everyone.
I'm really happy to have found DirectFB, I'm hoping it will help me to
achieve my goals of creating some intelligent digital signs.
I'm using a Pandaboard ES, which is running Ubunto 12.04.1 LTS with the
TI supplied OMAP drivers. I am not running X11 on this system and Wayland
isn't yet supported, but our old friend /dev/fb0 works fine :-)
I pulled a copy of DirectFB from git, built it natively using
--with-gfxdrivers=omap and it built and installed (woot!) and I can run
most of the demos (there are a few things that break from missing data
files but that is ok)
I would love it if I could get 2D acceleration, not sure if that is from
the omap driver or the pvr2d driver (which I did not build, but I could try
I suppose).
My first question is this one, when I run any dfb program (and dfbinfo as
(*) FBDev/Mode: Setting 1920x1080 RGB32
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit
(RGB32), pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument
(*) FBDev/Mode: Setting 1920x1080 RGB32
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit
(RGB32), pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument
D_INFO( "FBDev/Mode: Switched to %dx%d (virtual %dx%d) at %d bit
(%s), pitch %d\n",
var.xres, var.yres, var.xres_virtual, var.yres_virtual,
var.bits_per_pixel,
dfb_pixelformat_name(config->format),
shared->fix.line_length );
if (config->format == DSPF_RGB332)
dfb_fbdev_set_rgb332_palette();
else
dfb_fbdev_set_gamma_ramp( config->format );
This seems like it is trying to set a gamma ramp because the
config->format value isn't recognized as a truecolor format?
--Chuck
_______________________________________________
directfb-users mailing list
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

--
*
Never say that's "impossible", the word itself says "I'm Possible"
*

[Chuck McManis]

FWIW the TI folks claim that attempting to set this with the omapdrm driver
is a nop, it shouldn't fail like this but it also doesn't do anything, so
for now I've commented the code out in fbdev.c

--Chuck

On Sun, Aug 19, 2012 at 1:59 PM, haithem rahmani <

Post by haithem rahmani
Hello,
have you tried the ARGB pixelformat?
$>dfbinfo --dfb:pixelformat=ARGB

(*) FBDev/Mode: Setting 1920x1080 ARGB
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit
(ARGB), pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument
(*) FBDev/Mode: Setting 1920x1080 ARGB
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit
(ARGB), pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument
if (FBDEV_IOCTL( FBIOPUTCMAP, cmap ) < 0) {
D_PERROR( "DirectFB/FBDev: "
"Could not set gamma ramp" );
return errno2result(errno);
}
/proc/fb is '0 omapdrm' (which is to say the framebuffer is driven by the
omapdrm module) and apparently it chokes on the FBIOPUTCMAP ioctl. I'm
reaching out to the TI guys to see what they have to say as well.
--Chuck

Post by haithem rahmani
regards
Haithem

Post by Chuck McManis
Greetings everyone.
I'm really happy to have found DirectFB, I'm hoping it will help me to
achieve my goals of creating some intelligent digital signs.
I'm using a Pandaboard ES, which is running Ubunto 12.04.1 LTS with the
TI supplied OMAP drivers. I am not running X11 on this system and Wayland
isn't yet supported, but our old friend /dev/fb0 works fine :-)
I pulled a copy of DirectFB from git, built it natively using
--with-gfxdrivers=omap and it built and installed (woot!) and I can run
most of the demos (there are a few things that break from missing data
files but that is ok)
I would love it if I could get 2D acceleration, not sure if that is from
the omap driver or the pvr2d driver (which I did not build, but I could try
I suppose).
My first question is this one, when I run any dfb program (and dfbinfo
(*) FBDev/Mode: Setting 1920x1080 RGB32
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit
(RGB32), pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument
(*) FBDev/Mode: Setting 1920x1080 RGB32
(*) FBDev/Mode: Switched to 1920x1080 (virtual 1920x1080) at 32 bit
(RGB32), pitch 8192
(!) DirectFB/FBDev: Could not set gamma ramp --> Invalid argument
D_INFO( "FBDev/Mode: Switched to %dx%d (virtual %dx%d) at %d bit
(%s), pitch %d\n",
var.xres, var.yres, var.xres_virtual, var.yres_virtual,
var.bits_per_pixel,
dfb_pixelformat_name(config->format),
shared->fix.line_length );
if (config->format == DSPF_RGB332)
dfb_fbdev_set_rgb332_palette();
else
dfb_fbdev_set_gamma_ramp( config->format );
This seems like it is trying to set a gamma ramp because the
config->format value isn't recognized as a truecolor format?
--Chuck
_______________________________________________
directfb-users mailing list
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

--
*
Never say that's "impossible", the word itself says "I'm Possible"
*