mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Markus Rechberger" <mrechberger@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Mauro Carvalho Chehab" <mchehab@infradead.org>,
	linux-dvb-maintainer@linuxtv.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	video4linux-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB changes for 2.6.24
Date: Thu, 11 Oct 2007 06:50:12 +0200	[thread overview]
Message-ID: <d9def9db0710102150l3aa0626es90184c24875bc2e9@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0710101639550.20690@woody.linux-foundation.org>

On 10/11/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> On Thu, 11 Oct 2007, Markus Rechberger wrote:
> >
> > the chances of the em28xx are not accepted from my side since the latest
> code
> > which supports way more hardware is offtree for various reasons.
>
> Well, I've talked to various people, and none of the main kernel people
> end up being at all interested in a kernel that has external dependencies
> on binary blobs for tuners.
>

the drivers are all opensource and the code is available.

> So right now it seems like while I would personally want to have more
> vendors supprt their own drivers, if that in this case means that we'd
> have to have user-space and unmaintainable binaries to tune the cards,
> everybody seems to hate that idea.
>

For me the reason is that some drivers in the kernel which that driver
depends on are broken now. Those drivers got broken by several people
who disagree with me.
My conclusion after providing patches to fix those things is that I
won't run after those people anymore. I'm not going to have further
discussions with those people about it since there are enough other
outstanding things to do with that driver. After 1 1/2 years I'm just
fed up with it now and I want to continue to improve the driver.

> As such, the old and decrepit em28xx driver seems more useful to people,
> since at least it supports the limited set of hardware on its own.

it does not since it's broken and feature limited. On the other side
it requires a firmware from userspace too so I don't think it matters
at all if the algorithm is done in kernelspace or userspace since it
depends on such a blob (and I cannot get the source for that firmware,
if someone's interested in that he has to disassemble the firmware).

Markus

  reply	other threads:[~2007-10-11  4:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 21:50 Mauro Carvalho Chehab
2007-10-10 23:00 ` [v4l-dvb-maintainer] " Markus Rechberger
2007-10-10 23:24   ` Markus Rechberger
2007-10-10 23:35     ` Chuck Ebbert
2007-10-11  4:59       ` Markus Rechberger
2007-10-11  9:50         ` Aidan Thornton
2007-10-11 10:42           ` Pádraig Brady
2007-10-11 11:39             ` Markus Rechberger
2007-10-10 23:36   ` Andrew Morton
2007-10-11  5:09     ` Markus Rechberger
2007-10-11  5:32       ` Andrew Morton
2007-10-11  5:50         ` Markus Rechberger
2007-10-11  7:11       ` Dave Jones
2007-10-14 10:40     ` Markus Rechberger
2007-10-14 11:12       ` Hans Verkuil
2007-10-14 11:28         ` Markus Rechberger
2007-10-14 20:49       ` Johannes Stezenbach
2007-10-10 23:42   ` Linus Torvalds
2007-10-11  4:50     ` Markus Rechberger [this message]
2007-10-11  6:08       ` Aurelien Jarno
2007-10-11  6:31         ` Markus Rechberger
2007-10-11  9:33           ` Marcel Siegert
2007-10-11 10:20             ` Markus Rechberger
2007-10-11 12:54               ` Marcel Siegert
2007-10-11 13:01                 ` Markus Rechberger
2007-10-11 13:22           ` Aurelien Jarno

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=d9def9db0710102150l3aa0626es90184c24875bc2e9@mail.gmail.com \
    --to=mrechberger@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=video4linux-list@redhat.com \
    /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

Powered by JetHome