Re: MMC ioctl or sysfs interface?

[Jon Smirl <jonsmirl@gmail.com>]

On 6/12/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Sul, 2005-06-12 at 19:15, Pierre Ossman wrote:
> > Alan Cox wrote:
> > I wasn't aware that you could do ioctl on sysfs nodes. I guess I'll have
> > to dig a bit deeper in the documentation/code.
> 
> You can add support, but you'll need a device node one day anyway so you
> might as well give up on the sysfs only game - it doesn't IMHO work.

I have a sysfs interface for fbdev in the kernel -
/sys/class/graphics/fb0/*  It is working well for me and it's the only
interface EGL uses to access fbdev. It's all controllable with strings
that can be scripted if you want. If you play with it some of the
attributes are broken, there are fixes for them in the pipeline.

I also have DRM loaded for the same hardware. I'd have to think about
it for a while to see if DRM could go sysfs only. I'm using DRM to map
the framebuffer instead of fbdev.

One big difference is that a device node can carry session state. If
you open the device the file handle can track things belonging to the
session. With sysfs sessions are more of a mess. fbdev works cleanly
because there is no session state.

-- 
Jon Smirl
jonsmirl@gmail.com