From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux.dev, mchehab@kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Regression: v4l/bttv vbi vs iommu
Date: Sun, 13 Aug 2023 13:14:18 +0000 [thread overview]
Message-ID: <ZNjXKjCx3lH0s1m3@gallifrey> (raw)
In-Reply-To: <3a59ffba-a7fe-97b0-af76-7194f7b3896a@xs4all.nl>
* Hans Verkuil (hverkuil@xs4all.nl) wrote:
> On 03/02/2023 07:35, Christoph Hellwig wrote:
> > On Wed, Feb 01, 2023 at 09:48:46PM +0100, Hans Verkuil wrote:
> >> In fact, the plan is to replace the old and deprecated videobuf framework by the vb2
> >> framework in the bttv driver in the next 2-3 months or so. That will also automatically
> >> solve this problem.
> >
> > It would be great to expedite removal of the old videbuf code given
> > how many problems it has.
>
> We're working on it. A lot of old drivers in drivers/staging/media/deprecated will
> be removed in 6.3, and that leaves the cx18, bttv and saa7146 drivers that still use
> vb1.
>
> This week I posted patches converting cx18 to vb2 and someone else will work on the
> bttv conversion. We thought we could remove saa7146 as well, but it turns out that
> that is still very much in use (somewhat unexpectedly), so I plan to convert that
> one this month (I hope).
>
> I aim for removing vb1 in kernel 6.4 or 6.5.
Did this go in, I'm happy to give it a go if this is a world to test.
Dave
> Regards,
>
> Hans
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2023-08-13 13:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 16:26 Regression: v4l/bttv vbi vs iommu Dr. David Alan Gilbert
2023-02-01 20:48 ` Hans Verkuil
2023-02-02 3:04 ` Dr. David Alan Gilbert
2023-02-03 6:35 ` Christoph Hellwig
2023-02-03 8:05 ` Hans Verkuil
2023-08-13 13:14 ` Dr. David Alan Gilbert [this message]
2023-08-13 13:44 ` Hans Verkuil
2023-11-11 19:57 ` Dr. David Alan Gilbert
2023-11-13 14:38 ` Hans Verkuil
2023-11-14 0:31 ` Dr. David Alan Gilbert
2023-02-02 10:09 ` Christoph Hellwig
2023-02-02 17:09 ` Dr. David Alan Gilbert
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=ZNjXKjCx3lH0s1m3@gallifrey \
--to=dave@treblig.org \
--cc=hch@lst.de \
--cc=hverkuil@xs4all.nl \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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