All of lore.kernel.org
 help / color / mirror / Atom feed
From: wk <handygewinnspiel@gmx.de>
To: Alexey Klimov <klimov.linux@gmail.com>
Cc: Trent Piepho <xyzzy@speakeasy.org>,
	Douglas Schilling Landgraf <dougsland@gmail.com>,
	linux-media@vger.kernel.org
Subject: Re: [patch review 6/6] radio-mr800: redesign radio->users counter
Date: Sat, 08 Aug 2009 22:16:28 +0200	[thread overview]
Message-ID: <4A7DDD1C.1030906@gmx.de> (raw)
In-Reply-To: <208cbae30908081208o5a048fb0qdd6c356b0c6d3eb9@mail.gmail.com>

Alexey Klimov schrieb:
> On Sat, Aug 8, 2009 at 10:01 PM, Trent Piepho<xyzzy@speakeasy.org> wrote:
>   
>> On Sat, 8 Aug 2009, Alexey Klimov wrote:
>>     
>>> Redesign radio->users counter. Don't allow more that 5 users on radio in
>>>       
>> Why?
>>     
>
> Well, v4l2 specs says that multiple opens are optional. Honestly, i
> think that five userspace applications open /dev/radio is enough. Btw,
> if too many userspace applications opened radio that means that
> something wrong happened in userspace. And driver can handle such
> situation by disallowing new open calls(returning EBUSY). I can't
> imagine user that runs more than five mplayers or gnomeradios, or
> kradios and so on.
>
> Am i totally wrong here?
>
> Thanks.
>   
"I can't imagine.." Funny answer, reminds at the 640kB limit of old 
computers.. :)
But if there's no real technical restriction, the driver should not 
restrict access a device at all.


  reply	other threads:[~2009-08-08 20:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08 17:46 [patch review 6/6] radio-mr800: redesign radio->users counter Alexey Klimov
2009-08-08 18:01 ` Trent Piepho
2009-08-08 19:08   ` Alexey Klimov
2009-08-08 20:16     ` wk [this message]
2009-08-09  8:19       ` Hans Verkuil
2009-08-09 11:04         ` Alexey Klimov
2009-08-10 22:24 ` David Ellingsworth

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=4A7DDD1C.1030906@gmx.de \
    --to=handygewinnspiel@gmx.de \
    --cc=dougsland@gmail.com \
    --cc=klimov.linux@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=xyzzy@speakeasy.org \
    /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.