lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 4 Nov 2006 00:22:28 -0800 From: Greg KH <greg@...ah.com> To: Yu Luming <luming.yu@...il.com> Cc: Andrew Morton <akpm@...l.org>, Pavel Machek <pavel@....cz>, len.brown@...el.com, Matt Domsch <Matt_Domsch@...l.com>, Alessandro Guido <alessandro.guido@...il.com>, linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org, jengelh@...ux01.gwdg.de, gelma@...ma.net, ismail@...dus.org.tr, Richard Hughes <hughsient@...il.com> Subject: Re: [patch 4/6] Add output class document On Sat, Nov 04, 2006 at 09:22:00PM +0800, Yu Luming wrote: > Add output class document > > signed-off-by ? Luming.yu@...il.com > --- > [patch 4/6] Add output class document > video-output.txt | 34 ++++++++++++++++++++++++++++++++++ > 1 file changed, 34 insertions(+) > > diff --git a/Documentation/video-output.txt b/Documentation/video-output.txt > new file mode 100644 > index 0000000..71b1dba > --- /dev/null > +++ b/Documentation/video-output.txt > @@ -0,0 +1,34 @@ > + > + Video Output Switcher Control > + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + 2006 luming.yu@...il.com > + > +The output sysfs class driver is to provide video output abstract layer that > +can be used to hook platform specific methods to enable/disable video output > +device through common sysfs interface. For example, on my IBM Thinkpad T42 > +aptop, acpi video driver registered its output devices and read/write method > +for state with output sysfs class. The user interface under sysfs is : > + > +linux:/sys/class/video_output # tree . > +. > +|-- CRT0 > +| |-- device -> ../../../devices/pci0000:00/0000:00:01.0 > +| |-- state > +| |-- subsystem -> ../../../class/video_output > +| `-- uevent > +|-- DVI0 > +| |-- device -> ../../../devices/pci0000:00/0000:00:01.0 > +| |-- state > +| |-- subsystem -> ../../../class/video_output > +| `-- uevent > +|-- LCD0 > +| |-- device -> ../../../devices/pci0000:00/0000:00:01.0 > +| |-- state > +| |-- subsystem -> ../../../class/video_output > +| `-- uevent > +`-- TV0 > + |-- device -> ../../../devices/pci0000:00/0000:00:01.0 > + |-- state > + |-- subsystem -> ../../../class/video_output > + `-- uevent Use a struct device instead of a struct class_device please. That will change your tree a bit here (you will have symlinks at the top level. Have you been working with the X developers that have been doing a lot of work in describing and interacting with these different video devices? I think you might want to work with them so that you don't create an interface that will not be used by them. thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists