Thread: Linux Framebuffer Transparency

Hi,

I have been messing with the framebuffer on Linux with good results. But then I ran into a snag when trying to use the transparency field. I don't know if I need to enable an alpha channel for the framebuffer, I can't seem to find any references to this problem. But the following code doesn't seem to change the transparency at all.

Code:

// Declare includes.
#include <errno.h>
#include <fcntl.h>
#include <libgen.h>
#include <linux/fb.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <sys/ioctl.h>
#include <sys/mman.h>
#include <sys/stat.h>
#include <sys/types.h>
#include <unistd.h>

// Declare defines.
#define FRAMEBUFFER            "/dev/fb0"
#define PROGRAM_NAME_SIZE     50
#define SIZE_OF_MARK           4

// Declare stuctures.
struct _colour
{
    int blue;
    int green;
    int red;
    int transparency;
};

struct _info
{
    int fbfd;
    char *fbp;
    long screensize;
    struct fb_fix_screeninfo finfo;
    struct fb_var_screeninfo vinfo;
};

// Declare global variables.
char program_name[PROGRAM_NAME_SIZE + 1] = {0};

// Declare function prototypes.
void framebuffer_writing (void);
void get_info (struct _info *info);
void mark_row (int x, int y, int length, struct _info *info, struct _colour *colour);

int main (int argc, char *argv[])
{
// Get program name for error reporting.
    strcpy(program_name, basename(argv[0]));

// Check number of arguments.
    if(argc != 1)
    {
        fprintf(stderr, "Usage: %s\n", program_name);
        exit(EXIT_FAILURE);
    }

// Run process.
    framebuffer_writing();

// Exit cleanly.
    exit(EXIT_SUCCESS);
}

void framebuffer_writing (void)
{
// Declare variables.
    struct _info info = {0};
    struct _colour red = {0x00, 0x00, 0x87, 0x00};

// Get the framebuffer file descriptor.
    get_info(&info);

// Make gradient row.
    for(int a = 0; a < 255; a++, red.transparency++)
        mark_row(0 + (a * SIZE_OF_MARK), 300, 1, &info, &red);

// Used to show the transparency value was changed.
    printf("Transparency = %d\n", red.transparency);

// Unmap the framebuffer.
    munmap(info.fbp, info.screensize);
// Close framebuffer file descriptor.
    close(info.fbfd);
}

void get_info (struct _info *info)
{
// Open the framebuffer for reading and writing.
    if(((*info).fbfd = open(FRAMEBUFFER, O_RDWR)) == -1)
    {
        fprintf(stderr, "%s: %s error: open failed (%s) (%s)\n", program_name, __func__, strerror(errno), FRAMEBUFFER);
        exit(EXIT_FAILURE);
    }

// Get fixed screen information.
    if(ioctl((*info).fbfd, FBIOGET_FSCREENINFO, &(*info).finfo) == -1)
    {
        fprintf(stderr, "%s: %s error: ioctl failed (%s) (Error reading fixed information)\n", program_name, __func__, strerror(errno));
        exit(EXIT_FAILURE);
    }

// Get variable screen information.
    if(ioctl((*info).fbfd, FBIOGET_VSCREENINFO, &(*info).vinfo) == -1)
    {
        fprintf(stderr, "%s: %s error: ioctl failed (%s) (Error reading variable information)\n", program_name, __func__, strerror(errno));
        exit(EXIT_FAILURE);
    }

// Figure out the size of the screen in bytes.
    (*info).screensize = (*info).vinfo.xres * (*info).vinfo.yres * (*info).vinfo.bits_per_pixel / 8;

// Map the device to memory.
    if (((*info).fbp = (char *)mmap(0, (*info).screensize, PROT_READ | PROT_WRITE, MAP_SHARED, (*info).fbfd, 0)) == MAP_FAILED)
    {
        fprintf(stderr, "%s: %s error: mmap failed (%s)\n", program_name, __func__, strerror(errno));
        exit(EXIT_FAILURE);
    }
}

void mark_row (int x, int y, int length, struct _info *info, struct _colour *colour)
{
// Declare variables.
    long location = {0};

// Fill in a box on the framebuffer.
    for(int a = 0; a < SIZE_OF_MARK; a++)
        for(int b = 0; b < (SIZE_OF_MARK * length); b++)
        {
// Determine location of the pixel placement.
            location = (b + x + (*info).vinfo.xoffset) * ((*info).vinfo.bits_per_pixel / 8) + (a + y + (*info).vinfo.yoffset) * (*info).finfo.line_length;
// Set each colour for the pixel in question.
            *((*info).fbp + location) = (*colour).blue;
            *((*info).fbp + location + 1) = (*colour).green;
            *((*info).fbp + location + 2) = (*colour).red;
            *((*info).fbp + location + 3) = (*colour).transparency;
        }
}

Can someone please give a little insight into why the transparency might not be changing for me?

Thanx.

Originally Posted by john.c

The following says he's never seen transparency implemented.
https://kevinboone.me/linuxfbc.html

Very disappointing to hear. But ty for finding that.

Originally Posted by john.c

Also, don't say (*info).whatever. Instead say info->whatever.
And don't say *(a + i) but instead say a[i].

I will try to learn more on that. I don't have a lot of experience with '->' and '.'. It usually goes...

1) Write a statement involving a structure.
2) use '->' reference a struct variable.
3) Get an error regarding the use of '->'.
4) Change '->' to '.'.
5) Error disappears.

Basically if one doesn't work, the other one does. But you're right, I should learn to do it properly.

Ty for your time in correcting me. I really like the error handler for sure.

Originally Posted by Sir Galahad

I did notice that the program you've posted doesn't seem to write anything to the screen. Perchance do you have a more complete working example?

This is a simple example of basic drawing, it should work from the console. When you use xwindows, it won't show the framebuffer I use in my program. Dunno why. But if you can exit xwindows or wayland and go back to the console (tty), it should display a red line. If you're on a tty and it isn't visible, maybe increase the following:

Code:

#define SIZE_OF_MARK           4

Basically this all started from wanting to recreate the digital front cover of the "IT Crowd" dvd. I've got Moss all mapped out, but wanted to add the gradient background. Here is what I'm talking about:

What is meant here when you folks discuss "transparency"? Aren't we already discussing open source?

Originally Posted by john.c

Code:

const char *program_name; // don't need to copy the string
// in main: program_name = argv[0];

Sorry, I just noticed this. The reason why I use `basename` on the program name (or argv[0]) is because argv[0] depends on where and how the program is called.

Code:

ie:
$ run_my_program (in $PATH)    -    argv[0] = "run_my_program"
$ ./run_my_program             -    argv[0] = "./run_my_program"
$ /home/user/run_my_program    -    argv[0] = "/home/user/run_my_program"

I don't care where the program resides, when error reporting. So I strip it first thing. It's just cleaner to my eyes. And like I said, this is all in a template, I never have to type anything other than my desire to use `program_name` when I need to.