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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.LFD.0.999.0710101639550.20690@woody.linux-foundation.org>
Date:	Wed, 10 Oct 2007 16:42:19 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Markus Rechberger <mrechberger@...il.com>
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 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.

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. 

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.

		Linus
-
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/