Re: [Linux-fbdev-devel] re: James's new API post

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

> > Yes. For example floating point support in the kernel. I'd like to know 
> > how you'll persuade driver to know that '640x480-YUV422@59.94i' should be 
> > NTSC 800x525 interlaced picture, and how you'll center picture on screen
> > then? Where do you specify virtual xres and yres?
> >  
> Your overthinking it. For one, as long as modes are in a consistent format,
> it's easy for anyone to parse. And since people are already used to the
> "640x480-16@70" style format, what's the big deal?

With modedb it wouldn't be that much of a big step.

> As far as virtual xres and yres.. keep in mind this is a virtual filesystem..
> if your driver or subsystem has additional needs, you can simply register a
> new entry to deal with virtual resolution.. If you want a place for virtual
> resolution.. something like:
> 
> 	/dev/gfx/card0/frame0/resolution_virt
> 
> should suffice just fine. (Name pending).

Okay I see people got confussed over the ASCII thing. Yes Linus wants
ioctls to go away. There have been huge ioctl clashes in the past. Plus
Linus dreams of a network transparentancy. I also like that idea. So the
two things he wants to see go away are mmap and ioctl functionality. In
its place you create a file to represent the functionality of the device
and that you can read and write data to so its behavior changes. This data
can be binary or ASCII. It just has to be passed in via read and write.