public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Wouter Van Hemel <wouter-kernel@fort-knox.rave.org>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.8 pwc patches and counterpatches
Date: Fri, 27 Aug 2004 14:41:38 +0100	[thread overview]
Message-ID: <412F3A12.70709@grupopie.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0408271439040.578@senta.theria.org>

Wouter Van Hemel wrote:
> On Fri, 27 Aug 2004, Denis Vlasenko wrote:
> 
>> If you feel like it, you can even step up and maintain it.
>>
> 
> I really would, if it wouldn't be C, kernel makefile stuff_and_ driver 
> specifics. My current knowledge wouldn't do the driver justice, to say 
> it mildly.
> 
> Perhaps one of the maintainers of other webcam drivers could help out here.
> 
>>> Maybe Philips will open up their oh so secret compression algorithm 
>>> if we
>>> all ask them nicely. I mean, how secret can that still be?...
>>
>>
>> Corporations can be ridiculous/bureaucratic at times. Especially large 
>> ones.
>>
> 
> True, but I still think Philips was on the right track. I doubt that 
> their driver being pulled will aid linux support for their products...

I was really trying to restrain myself from entering this thread, but I 
can't help it anymore...

What do Phillips gain from making their compression code secret? (If it 
is really secret... I probably can reverse engineer it legally for the 
purpose of interoperability)

They are basically saying: "Yes the quality of our webcam is as bad as 
the competition, with the same low-quality cmos sensors, plastic lenses, 
high noise analog conditioning, etc. *but* we are so much better than 
our competitors because we have a secret compression algorithm that we 
don't want them to know because they can never figure out how to do a 
compression algorithm on their own..."

No, Phillips was *not* on the right track.

Hardware products should gain with _hardware_ merits. If the Phillips 
camera has a better lens, that allows more light in under ambient light, 
or some such, it is better than the competition.

The right track would be to provide all the hardware info so that a real 
open source driver could be written. (or even better, provide the open 
source driver themselves)

About the legal aspects of all this, they have been discussed 
extensively in the past. It is not about "hey this is just a simple 
hook", it is all about the derived work concept. This driver does 
absolutely nothing outside the kernel. It's only purpose is to attach 
itself to the kernel and to provide the images from the camera to 
userspace using the kernel ABI's. So you can not say it is not a derived 
work at all.

I for one, would really like to see Phillips allow Nemosoft to build a 
really open source driver, and not let all the work go to waste...

-- 
Paulo Marques - www.grupopie.com

  reply	other threads:[~2004-08-27 13:41 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 14:31 kernel 2.6.8 pwc patches and counterpatches city_hunter
2004-08-26 18:25 ` Wouter Van Hemel
     [not found]   ` <20040826190701.GA13310@kroah.com>
2004-08-26 23:35     ` Wouter Van Hemel
2004-08-26 23:40       ` Greg KH
2004-08-27  0:21         ` Wouter Van Hemel
     [not found]           ` <200408270917.47656.vda@port.imtp.ilyichevsk.odessa.ua>
2004-08-27 12:47             ` Wouter Van Hemel
2004-08-27 12:58               ` Xavier Bestel
2004-08-27 13:30                 ` Wouter Van Hemel
2004-08-27 13:04               ` Denis Vlasenko
2004-08-27 13:13                 ` Prakash K. Cheemplavam
2004-08-27 13:44                   ` Wouter Van Hemel
2004-08-27 23:18                     ` Rob van Nieuwkerk
2004-08-28  0:03                       ` Denis Vlasenko
2004-08-28  0:19                         ` James Courtier-Dutton
2004-08-28  0:50                       ` Craig Milo Rogers
2004-08-27 16:46                   ` Lee Revell
2004-08-27 13:35                 ` Wouter Van Hemel
2004-08-27  9:25   ` Christoph Hellwig
2004-08-27 12:56     ` Wouter Van Hemel
     [not found]   ` <buok6vldx4l.fsf@mctpc71.ucom.lsi.nec.co.jp>
2004-08-27 12:38     ` Wouter Van Hemel
     [not found]   ` <200408270845.38015.vda@port.imtp.ilyichevsk.odessa.ua>
2004-08-27 12:44     ` Wouter Van Hemel
2004-08-27 13:41       ` Paulo Marques [this message]
2004-08-27 13:58         ` Wouter Van Hemel
  -- strict thread matches above, loose matches on Subject: below --
2004-08-28  3:50 Thomas Winischhofer
2004-08-27 16:46 David McBride
2004-08-27 16:26 Kenneth Lavrsen
2004-08-27 16:51 ` Christoph Hellwig
2004-08-27 17:01 ` Greg KH
2004-08-27 17:34 ` Xavier Bestel
2004-08-27 18:09   ` David Woodhouse
2004-08-27 18:35     ` Vojtech Pavlik
2004-08-27 20:47       ` David Woodhouse
2004-08-27 21:18         ` Kenneth Lavrsen
2004-08-28 16:22   ` Brian Beattie
2004-08-27 18:08 ` Denis Vlasenko
2004-08-29 13:25 ` Alan Cox
2004-08-27 14:07 Thomas Winischhofer
2004-08-27 20:01 ` David S. Miller
2004-08-28  3:03   ` Thomas Winischhofer
2004-08-28  6:55     ` Arjan van de Ven
2004-08-28 14:46       ` Thomas Winischhofer
2004-08-28 17:13         ` Thomas Winischhofer
2004-08-29 13:28       ` Alan Cox
2004-08-29 15:00         ` Thomas Winischhofer
     [not found] <1092793392.17286.75.camel@localhost>
     [not found] ` <1092845135.8044.22.camel@localhost>
     [not found]   ` <20040823221028.GB4694@kroah.com>
2004-08-24 22:58     ` Nemosoft Unv.
2004-08-24 23:04       ` Greg KH
2004-08-25 14:02       ` Simon Oosthoek
2004-08-26  0:55       ` Rob van Nieuwkerk
2004-08-26  1:27         ` Rob van Nieuwkerk
2004-08-26  9:00       ` syrius.ml

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=412F3A12.70709@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=wouter-kernel@fort-knox.rave.org \
    /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