> > What I wish was done was the very first ioctl call was a generic ioctl
> > call to pass driver specific data. Basically you have something like this:
> > 
> > struct fb_driver_specific_data {
> >     __u32 magic_identifier;
> >     __u32 size_of_data_packet;
> >     char *data_buffer;
> > } 
> 
> It's called write(2). magic_identifier: which file we are writing to.
> size_of_data_packet: length. data_buffer: buffer we write from.
> 
> And if write() has too much overhead - we'd better fix _that_, because
> it's much more likely hotspot than ioctl ever will be.

I would use write except we use write to draw into the framebuffer. If I
write to the framebuffer with that data the only thing that will happen is
I will get pretty colors on my screen. 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to