> Well creating a new device wouldn't make linus happen right now. I do
> agree ioctl calls are evil!!!! You only have X amount of them. With write
> you can have infinte amounts of different functions to perform on a
> device. I didn't design fbdev :-( If I did it would have been far
> different. I do plan on some day merging drm and fbdev into one interface. So
> I plan to change this behavior. I like to see this interface ioctl-less
> (is their such a word ???). You mmap to alter buffers. Mmap is much more
> flexiable than write for graphics buffers anyways. You use write to pass
> "data" to the driver.
For data - maybe (but you lose any semblance of network transparency).
For commands? No fscking way in hell.
Look, we used to live in the world where every bloody action with
every bloody device required a special application (or macro, or
special library or equivalent abortion). It sucked. It _still_
sucks that way in CP/M and VMS lands.
The only reason for such suckitude is laziness. We shouldn't need to
do fscking voodoo to change modem speed. We shouldn't need it to change
font. We shouldn't need it to rewind tape or format disk. We _have_ to
do it because "ioctls are good enough and allow to do it fast, dirty and
without thinking about good APIs".
But guess what? mmap() also means that you need special applications.
mmap() also doesn't work over the network. You may need it as a performance
hack for massive data transfers, but if you hit memory bandwidth limitiations
on stuff like changing palette... Well, maybe you should spend time doing
something more productive. Like picking nose or masturbating.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/