public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kinz <jkinz@kinz.org>
To: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: Summarizing the PWC driver questions/answers
Date: Mon, 30 Aug 2004 14:24:40 -0400	[thread overview]
Message-ID: <20040830142440.A25964@redline.comcast.net> (raw)
In-Reply-To: <20040830173157.GA24392@top.worldcontrol.com>; from brian@worldcontrol.com on Mon, Aug 30, 2004 at 10:31:57AM -0700

On Mon, Aug 30, 2004 at 10:31:57AM -0700, Brian Litzinger wrote:
> > 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.

> I think Greg "chose" to take it out.

True, No one was holding a gun to his head.   :)

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

> I do not believe he "had no choice".  The guards at Auswitchs made the
> same argument at Nuremberg.  

[*** Nice "subtle" technique to call someone a Nazi. Real smooth!]

I "choose" to stop at stop signs and red lights.   Yay me.

> I disagree.  Binary drivers may take away from Linux and they may add to it.

My experiences: Binary drivers make Linux harder to support, harder to
distribute, harder to administrate and harder to maintain in production.

While they provide short term benefits, their long term impact is
negative. One example: What happens when company X goes out of business
or stops supporting the device?

A decision has been made: My understanding is that the Binary portion is 
moving to user space and the devices in question will still function
as a result.   

Please move it off the kernel list.

-- 
Idealism:  "Realism applied over a longer time period"

Jeff Kinz

  reply	other threads:[~2004-08-30 18:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 16:26 Summarizing the PWC driver questions/answers Greg KH
2004-08-27 16:58 ` 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 [this message]
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=20040830142440.A25964@redline.comcast.net \
    --to=jkinz@kinz.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox