Re: [linux-fbdev] [ANNOUNCE] vesafb full VBE 2.0 support

• Next message: root: "2.3.40 unresolved symbol(s)"
• Previous message: Norman Back: "inodes are no longer constant across VFAT mounts at kernel 2.2.14"
• In reply to: Jeff Garzik: "Re: [linux-fbdev] [ANNOUNCE] vesafb full VBE 2.0 support"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sun, 23 Jan 2000, Jeff Garzik wrote:
> Looks cool, but do you need an extra device?

Currently yes.

> You should add custom ioctls to /dev/fb for this purpose if at all
> possible...

Hmm. now that I think about it, that could work. My very first solution
was proc-based then I went for ioctls but dropped it for the
device. Guess I had some brain damage going on there because I was trying
to send file descriptor of a pipe via ioctl to vesafb. And that was
obviously a horrible approach but you could simply sleep in the ioctl and
do all the communication that way.

-- 
D.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: root: "2.3.40 unresolved symbol(s)"
• Previous message: Norman Back: "inodes are no longer constant across VFAT mounts at kernel 2.2.14"
• In reply to: Jeff Garzik: "Re: [linux-fbdev] [ANNOUNCE] vesafb full VBE 2.0 support"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:29 EST