LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Manu Abraham <abraham.manu@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Soeren Moch <smoch@web.de>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Regression 5.14] media: dvb userspace api
Date: Wed, 25 Aug 2021 08:25:57 +0530	[thread overview]
Message-ID: <CAHFNz9L29LK+L8LjqyTyqq3LsvzeA6iYFHwP9n3uNBbqbbm1bg@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wjSadWPfzQ_hOqbjq6c_xwJs8GLHTyznhXRvDF5Yrs4FA@mail.gmail.com>

On Mon, Aug 23, 2021 at 10:30 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> I have reverted the header file move. But I would also heartily
> recommend that whatever user program includes those headers (VDR -
> anything else?) should take snapshots of these specific kernel
> headers.
>
> I'm not convinced that it makes sense to move the av7110 driver back
> from staging - it may continue to work, but it _is_ old and there is
> no maintenance - and I would certainly suggest that any other
> out-of-tree driver that uses these old interfaces that nothing else
> implements shouldn't do so, considering that nothing else implements
> them.

Sorry for barging in between your discussion, but it seemed like you really
missed some perspective and hence.

My 2 cents worth:
* Revert the header changes.

* Let someone else with knowledge of it take over the maintenance
of the av7110 driver.

  - This would allow other hardware also to be easily accommodated
in a similar manner.

* Pull the out of tree drivers and allocate maintenance of those, to
someone who understands them. Don't you want more hardware to be
supported out of the box ?

Should there be no driver for those DVB output hardware, but only for
V4L2 output devices ?

There exists other hardware which As a person who worked on another
av7110 like driver (saa716x based s2 6400), which I can confirm.
The API is supposed to simplify life, not make it even more complex.
These devices would need lot of workarounds to work with the API that
which Mauro advocates, which might even break those drivers given
their complexity and size.

It would make life a lot easier for the users, Mauro himself and
this long never ending discussion can be put to rest.

Thanks,
MA

  parent reply	other threads:[~2021-08-25  2:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 12:15 Soeren Moch
2021-08-19 11:31 ` Mauro Carvalho Chehab
2021-08-21 13:58   ` Manu Abraham
2021-08-22 15:21   ` Soeren Moch
2021-08-22 17:47     ` Mauro Carvalho Chehab
2021-08-23 14:59       ` Soeren Moch
2021-08-23 16:58         ` Linus Torvalds
2021-08-23 20:16           ` Soeren Moch
2021-08-24  7:47           ` Mauro Carvalho Chehab
2021-08-24 20:01             ` Honza P
2021-08-25  2:55           ` Manu Abraham [this message]
2021-08-25  6:33             ` Mauro Carvalho Chehab
2021-08-25 16:16               ` Manu Abraham
2021-08-26 12:26                 ` Mauro Carvalho Chehab

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=CAHFNz9L29LK+L8LjqyTyqq3LsvzeA6iYFHwP9n3uNBbqbbm1bg@mail.gmail.com \
    --to=abraham.manu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=smoch@web.de \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [Regression 5.14] media: dvb userspace api' \
    /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

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).