From: Michael Krufky <mkrufky@m1k.net>
To: Johannes Stezenbach <js@linuxtv.org>
Cc: Andrew Morton <akpm@osdl.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Mauro Carvalho Chehab <mauro_chehab@yahoo.com.br>,
Michael Krufky <mkrufky@linuxtv.org>,
Linux and Kernel Video <video4linux-list@redhat.com>,
linux-kernel@vger.kernel.org, rbultje@ronald.bitfreak.net,
middelin@polyware.nl
Subject: Re: Fw: zoran drivers: absense of locking?
Date: Fri, 28 Oct 2005 21:45:04 -0400 [thread overview]
Message-ID: <4362D420.5040809@m1k.net> (raw)
In-Reply-To: <20051029013252.GC15903@linuxtv.org>
Johannes Stezenbach wrote:
>On Fri, Oct 28, 2005 Andrew Morton wrote:
>
>
>>Alexey, please don't assume that everyone reads lkml.
>>
>>
>I Cc: the v4l people, maybe they can answer the question.
>
>Johannes
>
>
>
It's not in our tree... This is what I can see in the MAINTAINERS file:
ZR36067 VIDEO FOR LINUX DRIVER
P: Ronald Bultje
M: rbultje@ronald.bitfreak.net
L: mjpeg-users@lists.sourceforge.net
W: http://mjpeg.sourceforge.net/driver-zoran/
S: Maintained
ZR36120 VIDEO FOR LINUX DRIVER
P: Pauline Middelink
M: middelin@polyware.nl
W: http://www.polyware.nl/~middelin/En/hobbies.html
W: http://www.polyware.nl/~middelin/hobbies.html
S: Maintained
I can only guess that this falls under ZR36067 ?? (cc's added)
>>Begin forwarded message:
>>
>>Date: Sat, 29 Oct 2005 01:16:47 +0400
>>From: Alexey Dobriyan <adobriyan@gmail.com>
>>To: linux-kernel@vger.kernel.org
>>Subject: zoran drivers: absense of locking?
>>
>>
>>I've tried to read random part of a tree and now scratching my head
>>with a question:
>>
>> what protects the number and a list of registered codecs in
>> zoran drivers?
>>
>>Example: drivers/media/video/zr36050.c:
>>
>> /* amount of chips attached via this driver */
>> static int zr36050_codecs = 0;
>>
>>Decremented in zr36050_unset().
>>Checked for maximum value, used and incremented in zr36050_setup().
>>
>>[Assigment to 0 in zr36050_init_module is not needed. dprintk() in
>>zr36050_cleanup_module() should be converted to BUG_ON, so I'll ignore
>>them.]
>>
>> zr36050_codecs
>> zr36050_unset() = struct videocodec::unset
>> zr36050_setup() = struct videocodec::setup
>>
>>The only place where ->unset and ->setup methods are called is
>>drivers/media/video/videocodec.c:
>>
>> zr36050_codecs
>> zr36050_unset()
>> videocodec_detach()
>> zr36050_setup()
>> videocodec_attach()
>>
>>Both videocodec functions are exported.
>>
>>No spinlocks or semaphores in sight.
>>
>>Does anybody know what protects the list of registered codecs in zoran
>>drivers?
>>
>>-
>>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/
>>
next parent reply other threads:[~2005-10-29 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051028163219.340fa347.akpm@osdl.org>
[not found] ` <20051029013252.GC15903@linuxtv.org>
2005-10-29 1:45 ` Michael Krufky [this message]
2005-10-29 4:02 ` Fw: zoran drivers: absense of locking? Ronald S. Bultje
2005-10-30 10:03 ` Pauline Middelink
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=4362D420.5040809@m1k.net \
--to=mkrufky@m1k.net \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=js@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mauro_chehab@yahoo.com.br \
--cc=middelin@polyware.nl \
--cc=mkrufky@linuxtv.org \
--cc=rbultje@ronald.bitfreak.net \
--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