Messages in this thread | | | Date | Tue, 21 Sep 2004 14:45:07 +0200 | From | Pavel Machek <> | Subject | Re: Design for setting video modes, ownership of sysfs attributes |
| |
Hi!
> 1) user owns graphics devices > 2) user sets mode with string (or similar) format using ioctl common to > all drivers. > 3) driver is locked to prevent multiple mode sets > 4) common code takes this string and does a hotplug event with it.
I though this was
"Driver decides to either do it itself in kernel, or call userspace helper if that would be too complex".
> How are errors going to be communicated in this scheme? I can cat the > sysfs mode variable to get a status. Is there a good way to do this > without polling?
I'd say that write() to that sysfs file can simply return error. See echo disk > /sys/power/state, it returns error if transition failed.
Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - 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/
| |