RE: [Linux-fbdev-devel] fbdev API problems

[James S. <jsi...@tr...>]

> I've though of several use cases that make the current way of doing
> things just unworkable.

Okay. We have many cases where this is broken.

[snip]..

> I think you misinterpreted one of my functions....plus I left one
> out.
> 
> fb_put     (Set a chunk of the framebuffer from the data provided. The
>             data comes fro userland or kernelland)
> fb_set     (The a chunk of the framebuffer to a single value)
> fb_get     (Get a chunk of data fro the framebuffer to the place
>             requested. It can be userland or kernelland)
> fb_copy    (aka blit, screen_to_screen)

Okay. I'm warming up to this idea. Actually what I'm thinking is we have
header filies for various graphics cards and each graphics card has a 

#include <linux/fb.h>

Now in say each graphics card header we place a inline function that
userland can use as well as the kernel for doing the basic functions:

fb_put_pixels
fb_get_pixels
fb_memset
fb_rectfill
fb_copyarea
fb_imageblit

Just have the basic functions for the kernel tho. Lets not get crazy here.
 
> This is hard for me to swallow since "what we have" cannot possibly
> work for what I'm trying to do. It will only get worse if mmap
> goes away.

What I mean is the ideas are floating around but I can't keep track of
everything. 

> I am writing up all the concepts I have floating around in my head
> and I'll post it when I'm done. I have to believe that fixing all
> the major issues is easier than trying to fix small parts.

Okay. That would be good.