From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Christian Zigotzky <chzigotzky@xenosoft.de>, linux-media@vger.kernel.org
Cc: Darren Stevens <darren@stevens-zone.net>,
mad skateman <madskateman@gmail.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Deborah Brouwer <deborahbrouwer3563@gmail.com>
Subject: Re: [BTTV] [FSL P50x0] [PASEMI] TV Time doesn't work anymore after dropping the overlay support
Date: Fri, 5 May 2023 08:45:41 +0200 [thread overview]
Message-ID: <a02d481b-562c-803a-a71d-b8d95ba7ebb5@xs4all.nl> (raw)
In-Reply-To: <79ea7cc5-6981-a791-7fed-7a6e27225000@xenosoft.de>
On 05/05/2023 08:25, Christian Zigotzky wrote:
> On 02 May 2023 at 08:57 am, Hans Verkuil wrote:
>> If v4l2-ctl fails, then try again
>> after applying this series:
>>
>> https://patchwork.linuxtv.org/project/linux-media/cover/cover.1682995256.git.deborah.brouwer@collabora.com/
> Your patch series solved the issue. Thanks a lot!
Nice, but somewhat unexpected :-)
I'm a little bit unsure how to proceed: the 6.4 kernel will remove destructive overlay
support, but it won't have this series yet, that's for 6.5. But that would make 6.4
unusable for you.
I might have to revert the overlay removal, at least for bttv.
Regards,
Hans
next prev parent reply other threads:[~2023-05-05 6:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 14:09 [BTTV] [FSL P50x0] [PASEMI] TV Time doesn't work anymore after dropping the overlay support Christian Zigotzky
2023-05-01 15:20 ` Christian Zigotzky
2023-05-02 6:57 ` Hans Verkuil
2023-05-05 6:25 ` Christian Zigotzky
2023-05-05 6:45 ` Hans Verkuil [this message]
2023-05-05 7:20 ` Christian Zigotzky
2023-09-04 11:51 ` Christian Zigotzky
2023-09-04 12:02 ` Christian Zigotzky
2023-09-07 15:23 ` Hans Verkuil
2023-09-07 15:49 ` Christian Zigotzky
2023-09-10 2:33 ` Deborah Brouwer
2023-09-11 9:51 ` Hans Verkuil
2023-09-14 7:01 ` Hans Verkuil
2023-09-10 11:19 Christian Zigotzky
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=a02d481b-562c-803a-a71d-b8d95ba7ebb5@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=deborahbrouwer3563@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=madskateman@gmail.com \
--cc=rtd2@xtra.co.nz \
/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;
as well as URLs for NNTP newsgroup(s).