lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c6d5be4c-42c9-b8fa-fbd7-108c5da694bc@chromium.org>
Date:   Tue, 11 Apr 2023 16:31:15 +0900
From:   Max Staudt <mstaudt@...omium.org>
To:     Hans Verkuil <hverkuil@...all.nl>,
        Mauro Carvalho Chehab <mchehab@...nel.org>
Cc:     linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
        Ricardo Ribalda <ribalda@...omium.org>,
        Yunke Cao <yunkec@...omium.org>,
        Tomasz Figa <tfiga@...omium.org>
Subject: Re: [PATCH v1] media: vivid: Add webcam parameter for (un)limited
 bandwidth

On 4/11/23 16:26, Hans Verkuil wrote:
> I think we either use this bandwidth option and calculate the max fps based on
> that (basically the bandwidth divided by (image_size + some blanking factor)),
> or we keep it simple and instead of going down two steps in fps we allow up to
> 60 fps up to 720p, then 30 fps for 1080p and 15 fps for 4k.
> 
> The fps values currently used are a bit outdated w.r.t. modern webcams, so
> upgrading it wouldn't hurt. And this is a lot simpler than doing bandwidth
> calculations.

Do I understand you correctly, are you suggesting to simply update the 
FPS limits to a new fixed schema, and not have an option at all?

I'm happy to prepare an alternative patch for that, too.



Max

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ