linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: root@mauve.demon.co.uk
To: mark@alpha.dyndns.org (Mark McClelland)
Cc: greg@kroah.com (Greg KH), kraxel@bytesex.org (Gerd Knorr),
	linux-kernel@vger.kernel.org (Kernel List),
	video4linux-list@redhat.com (video4linux list)
Subject: Re: [RFC/PATCH] sysfs'ify video4linux
Date: Wed, 16 Jul 2003 15:10:22 +0100 (BST)	[thread overview]
Message-ID: <200307161410.PAA04171@mauve.demon.co.uk> (raw)
In-Reply-To: <3F15540E.2040405@alpha.dyndns.org> from "Mark McClelland" at Jul 16, 2003 06:33:02 AM

> 
> Greg KH wrote:
> 
> >On Tue, Jul 15, 2003 at 04:31:19PM +0200, Gerd Knorr wrote:
> >  
> >
> >>Changes required/recommended in video4linux drivers:
> >>
> >>  * some usb webcam drivers (usbvideo.ko, stv680.ko, se401.ko 
> >>    and ov511.ko) use the video_proc_entry() to add additional
> >>    procfs files.  These drivers must be converted to sysfs too
> >>    because video_proc_entry() doesn't exist any more.
<snip>
> >Is there any need for these drivers to export anything through sysfs now
> >instead of /proc?
> >
> 
> Yes, at least with ov511. Some of the info that it puts in /proc is no 
> longer necessary. However, there are various bits of hardware info that 
> still need to get to userspace, for scripts that need to tell otherwise 
> identical (same VID/PID/revision) cameras apart when creating /dev nodes.

Also, there is some other information that scripts need.
Exposure gives information about light levels, which can be used to 
compute the absolute brightness of a scene captured.


  reply	other threads:[~2003-07-16 13:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 14:31 [RFC/PATCH] sysfs'ify video4linux Gerd Knorr
2003-07-15 15:21 ` Ronald Bultje
2003-07-15 16:19   ` Matt Porter
2003-07-15 21:27 ` Greg KH
2003-07-16  8:44   ` Gerd Knorr
2003-07-16 16:19     ` Greg KH
2003-07-16 20:20       ` Gerd Knorr
2003-07-16 21:08         ` Greg KH
2003-07-17 12:01           ` Gerd Knorr
2003-07-17 14:57             ` Greg KH
2003-07-17 16:37               ` Gerd Knorr
2003-07-17 21:49                 ` Greg KH
2003-07-18  9:59                   ` Gerd Knorr
     [not found]                     ` <20030718234359.GK1583@kroah.com>
2003-07-21  7:28                       ` Gerd Knorr
2003-07-21  7:55                         ` Ronald Bultje
2003-07-21 15:43                         ` [RFC/PATCH] 1/2 v4l: sysfs'ify video4linux core Gerd Knorr
2003-07-21 15:47                           ` [RFC/PATCH] 2/2 v4l: sysfs'ify bttv driver Gerd Knorr
2003-07-21 16:27                           ` [RFC/PATCH] 1/2 v4l: sysfs'ify video4linux core Greg KH
2003-07-16 13:33   ` [RFC/PATCH] sysfs'ify video4linux Mark McClelland
2003-07-16 14:10     ` root [this message]
2003-07-16 16:23     ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200307161410.PAA04171@mauve.demon.co.uk \
    --to=root@mauve.demon.co.uk \
    --cc=greg@kroah.com \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@alpha.dyndns.org \
    --cc=video4linux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).