All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Summarizing the PWC driver questions/answers
Date: Fri, 27 Aug 2004 09:26:13 -0700	[thread overview]
Message-ID: <20040827162613.GB32244@kroah.com> (raw)

So, I've gotten a lot of emails about this topic, so I'll just answer
them all here in public, and point people at them when they ask them
again:

First off, here's Nemosoft's big post about the driver, please read that
first, and the responses to that thread:
http://thread.gmane.org/gmane.linux.usb.devel/26310

And here's Linus's response after I removed the driver, when Nemosoft
asked me to:
http://thread.gmane.org/gmane.linux.kernel/229968

Oh, and there's now a lwn.net thread too:
http://lwn.net/Articles/99615/

Ok, on to the questions:

Q: Why did you remove the hook from the pwc driver?
A: It was there for the explicit purpose to support a binary only
   module.  That goes against the kernel's documented procedures, so I
   had to take it out.

Q: That hook had been in there for years!  Why did you suddenly decide
   to remove it now?
A: I was really not aware of the hook, and the fact that it was only
   good for a binary module to use.  I'm sorry, I should have realized
   this years ago, but I didn't.  Recently someone pointed this hook out
   to me, and the fact that it really didn't belong in there due to the
   kernel's policy of such hooks.  So, once I became aware of it, I had
   no choice but to remove it.

Q: Why did you delete the whole pwc driver from the tree?
A: That is what the original author (Nemosoft) wanted to happen.  It was
   his request, and I honored it.  Go ask him why he wanted it out if
   you are upset about this, I merely accepted his decision as he was
   the current maintainer and author of the code.

Q: But you took away my freedom!  Isn't Linux about freedom?
A: Again, it was Nemosoft's decision.  The kernel also has to abide by
   it's documented procedures, so that is why the hook had to go.
   Remember, the original driver was released under the GPL, so you are
   free to take that code and maintain it if you so desire.  I'd gladly
   support someone taking the GPL code and agreeing to maintain it, and
   resubmitting it for inclusion in the main kernel tree.  That's the
   freedom that Linux provides, no closed source OS would allow you to
   do that, if a company pulled support for a product (which happens all
   the time.)

Q: You jerk, I had invested lots of money in this camera, you are
   costing me money by ripping it out.  You should be ashamed of
   yourself!
A: See the above question about freedom.  If it means that much to you,
   then offer to maintain the code, it's that simple.

Q: You are keeping companies from wanting to write binary drivers for
   Linux.
A: Duh!  What do you think all of the kernel developers have been
   stating for years, in public.  Binary drivers only take from Linux,
   they do not give back anything.  See Andrew Morton's OLS 2004 keynote
   address for more information and background on this topic.

Q: You are a fundamentalist turd / jerk / pompous ass /
   GNU-freebeer-biased-idiot-fundamentalist fucktard / ignorant slut!
A: I've been called worse by better people, get over yourself.


             reply	other threads:[~2004-08-27 16:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 16:26 Greg KH [this message]
2004-08-27 16:58 ` Summarizing the PWC driver questions/answers David Woodhouse
2004-08-27 18:26   ` Wouter Van Hemel
2004-08-27 19:05     ` Ian Romanick
2004-08-27 20:36       ` Wouter Van Hemel
2004-08-27 16:58 ` Prakash K. Cheemplavam
2004-08-27 17:54 ` Roman Zippel
2004-08-27 18:51 ` [linux-usb-devel] " Alan Stern
2004-08-27 20:31   ` Greg KH
2004-08-30 17:31 ` Brian Litzinger
2004-08-30 18:24   ` Jeff Kinz
2004-08-30 19:28   ` viro
2004-08-30 20:11   ` Kenneth Lavrsen
  -- strict thread matches above, loose matches on Subject: below --
2004-08-27 19:54 Kenneth Lavrsen
2004-08-27 20:22 ` David S. Miller
2004-08-27 20:30 ` David Ford
2004-08-27 21:26   ` Wouter Van Hemel
2004-08-27 20:32 ` Zwane Mwaikambo
2004-08-27 21:25 ` Jesper Juhl
     [not found]   ` <Pine.LNX.4.61.0408272259450.2771@dragon.hygekrogen.localho st>
2004-08-27 22:08     ` Kenneth Lavrsen
2004-08-27 23:01       ` Bernd Petrovitsch
2004-08-28  0:22       ` Paul Jakma
2004-08-30 12:04 ` Geert Uytterhoeven
2004-08-28 21:07 linux
2004-08-28 22:06 ` Oliver Neukum

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=20040827162613.GB32244@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.