From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: V4L <video4linux-list@redhat.com>
Subject: Re: [PATCH] Add ov772x driver
Date: Thu, 16 Oct 2008 08:35:19 +0200 [thread overview]
Message-ID: <8763ntf3o8.fsf@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0810160814190.3892@axis700.grange> (Guennadi Liakhovetski's message of "Thu\, 16 Oct 2008 08\:24\:40 +0200 \(CEST\)")
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> Hm, so, to test your camera you have to modify your source and rebuild
> your kernel... And same again to switch back to normal operation. Does not
> sound very convenient to me. OTOH, making it a module parameter makes it
> much easier. In fact, maybe it would be a good idea to add a new
> camera-class control for this mode. Yet another possibility is to enable
> debug register-access in the driver and use that to manually set the test
> mode from user-space. A new v4l-control seems best to me, not sure what
> others will say about this. As you probably know, many other cameras also
> have this "test pattern" mode, some even several of them. So, this becomes
> a control with a parameter then.
Personnaly I'm rather inclined for the debug registers solutions.
When developping a camera driver, the test pattern alone is not enough. You have
to tweak the registers, see if the specification is correct, then understand the
specification, and then change your driver code. My experience tells me you
never understand correctly are camera setup from the first time.
So IMHO the registers are enough here.
> Then a new control or raw register access would be a better way, I think.
So do I.
Cheers.
--
Robert
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-10-16 6:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 10:52 [PATCH] Add ov772x driver Kuninori Morimoto
2008-10-15 23:41 ` Guennadi Liakhovetski
2008-10-16 1:28 ` morimoto.kuninori
2008-10-16 2:21 ` Magnus Damm
2008-10-16 6:24 ` Guennadi Liakhovetski
2008-10-16 6:35 ` Robert Jarzmik [this message]
2008-10-16 6:46 ` Magnus Damm
2008-10-16 6:55 ` Hans Verkuil
2008-10-16 6:58 ` Magnus Damm
2008-10-16 6:49 ` Magnus Damm
-- strict thread matches above, loose matches on Subject: below --
2008-10-16 4:28 Kuninori Morimoto
2008-10-16 8:27 ` Antonio Ospite
2008-10-16 9:53 ` morimoto.kuninori
2008-10-16 10:36 ` Magnus Damm
2008-10-16 19:23 ` Guennadi Liakhovetski
2008-10-16 20:58 ` Hans Verkuil
2008-10-17 2:47 ` Magnus Damm
2008-10-17 6:50 ` Guennadi Liakhovetski
2008-10-17 7:55 ` Magnus Damm
2008-10-17 8:38 ` Guennadi Liakhovetski
2008-10-17 9:31 ` Magnus Damm
2008-10-17 7:41 ` Antonio Ospite
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=8763ntf3o8.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=g.liakhovetski@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.