From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>, linux-media@vger.kernel.org
Subject: Re: Proposal: removal of old vb1 or custom streaming I/O drivers
Date: Wed, 10 Aug 2022 19:05:16 +0200 [thread overview]
Message-ID: <20220810190516.466cfca2@coco.lan> (raw)
In-Reply-To: <630bf451-28a0-91d2-5e55-b95bcbde82d0@redhat.com>
Em Wed, 10 Aug 2022 16:27:03 +0200
Hans de Goede <hdegoede@redhat.com> escreveu:
> >> And for bt8xx I would probably be willing to convert it to vb2 as well,
> >> provided we can strip the overlay support from the driver (since, if memory
> >> serves, vb2 doesn't support that) and convert it to vb2. It's a big job, though.
> >
> > It sounds OK on my eyes to remove overlay support from bt8xx during VB2
> > conversion. We should probably add a warning about such removal before
> > that (see below).
>
> About bt8xx support. At least in the Netherlands the cable companies have
> stopped sending analog TV over the cable (only DVB now) so I've remove
> my bt8xx tv-card from my machine after many years of using it.
>
> I believe something similar is happening in most of the rest of Europe
> at least.
This has nothing to do with analog TV. There are several bt8xx, saa713x
and cx18 products focused on video surveillance systems. Basically,
analog cameras connected to the capture boards using coaxial cables,
like those:
https://www.camsecure.co.uk/Camsecure_video_capture_cards.html
Yeah, those are also being deprecated with time with IP-based cameras,
but still there are a lot of such products using analog ones out there.
Funny enough, even analog TV seems to still be used on some places. We
recently merged some patches addressing some issues with PAL/N' on
some drivers.
Thanks,
Mauro
next prev parent reply other threads:[~2022-08-10 17:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 11:35 [ANN] Media Summit at ELCE Dublin, September 12: Draft Agenda V1 Hans Verkuil
2022-08-05 13:25 ` Laurent Pinchart
2022-08-22 8:21 ` Benjamin MUGNIER
2022-08-05 14:56 ` Hans Verkuil
2022-08-09 9:38 ` Michael Tretter
2022-08-09 10:38 ` Hans Verkuil
2022-08-09 10:18 ` Michael Olbrich
2022-08-09 10:39 ` Hans Verkuil
2022-08-09 13:01 ` Hans Verkuil
2022-08-09 13:02 ` Laurent Pinchart
2022-08-10 8:18 ` Proposal: removal of old vb1 or custom streaming I/O drivers Hans Verkuil
2022-08-10 10:24 ` Mauro Carvalho Chehab
2022-08-10 11:53 ` Laurent Pinchart
2022-08-10 14:27 ` Hans de Goede
2022-08-10 17:05 ` Mauro Carvalho Chehab [this message]
2022-08-18 1:33 ` [ANN] Media Summit at ELCE Dublin, September 12: Draft Agenda V1 Niklas Söderlund
2022-08-18 7:04 ` Hans Verkuil
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=20220810190516.466cfca2@coco.lan \
--to=mchehab@kernel.org \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox