linux-kernel - Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB changes for 2.6.24

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d9def9db0710102150l3aa0626es90184c24875bc2e9@mail.gmail.com>
Date:	Thu, 11 Oct 2007 06:50:12 +0200
From:	"Markus Rechberger" <mrechberger@...il.com>
To:	"Linus Torvalds" <torvalds@...ux-foundation.org>
Cc:	"Mauro Carvalho Chehab" <mchehab@...radead.org>,
	linux-dvb-maintainer@...uxtv.org,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	video4linux-list@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB changes for 2.6.24

On 10/11/07, Linus Torvalds <torvalds@...ux-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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/