archive mirror
 help / color / mirror / Atom feed
From: Mark McClelland <>
To: Greg KH <>
Cc: Gerd Knorr <>,
	Kernel List <>,
	video4linux list <>
Subject: Re: [RFC/PATCH] sysfs'ify video4linux
Date: Wed, 16 Jul 2003 06:33:02 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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.
>I'd be glad to do this work once your change makes it into the core. 

I can do the ov511 work if you want. I can have it done in two days (or 

>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.

Is there a convention for naming driver-specific files in /sys? E.g.: 
ov511_foo, _foo, etc...? I don't want to pollute the namespace.

>From what I remember, it only looked like debugging and other general info stuff.

There *is* some debugging stuff I would like to keep, at least for now. 
Approximately half of the bug reports I get are resolved after I see the 
user's /proc info. Is it acceptable to put it all in one file, since it 
isn't meant to be machine-parseable anyway? Some of the HCI drivers do 
that, right?

Mark McClelland

  parent reply	other threads:[~2003-07-16 13:18 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]                     ` <>
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   ` Mark McClelland [this message]
2003-07-16 14:10     ` [RFC/PATCH] sysfs'ify video4linux root
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:

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

  git send-email \ \ \ \ \ \ \

* 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).