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: <20070914135237.GB19311@devserv.devel.redhat.com>
Date:	Fri, 14 Sep 2007 09:52:37 -0400
From:	Alan Cox <alan@...hat.com>
To:	Markus Rechberger <mrechberger@...il.com>
Cc:	Steven Toth <stoth@...ppauge.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"video4linux-list@...hat.com" <video4linux-list@...hat.com>,
	"linux-dvb@...uxtv.org" <linux-dvb@...uxtv.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [linux-dvb] [PATCH] Userspace tuner

On Fri, Sep 14, 2007 at 01:17:05AM +0200, Markus Rechberger wrote:
> what stops vendors of using the current existing code to achieve that
> goal. They could provide binary drivers with the existing API.

If you feel lucky about the GPL

> What stops companies to intercept the ioctl calls and overriding some
> I2C commands?

The GPL - derivative work is the boundary not code linkage. Possibly a userspace
tuner hack would probably fit this too. Especially if a specific vendor is
producing both bits together and trying to claim they are independant.

> How about proprietary video formats, would you also place the decoding
> algorithms in kernel  just to force companies to release their code
> for it?

No, I would assume they'd provide a proprietary conversion library that
no nobody would use (just like their hw). We keep format conversion firmly
seperated from hardware I/O processing. 

Alan

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ