mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Benjamin Bach" <benjamin@overtag.dk>
Cc: "Arjan van de Ven" <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Idea: Automatic binary driver compiling system
Date: Sat, 18 Mar 2006 17:12:25 +0100	[thread overview]
Message-ID: <9a8748490603180812n1fda55bfq8909e118cc6dc3cc@mail.gmail.com> (raw)
In-Reply-To: <441C2CF6.1050607@overtag.dk>

On 3/18/06, Benjamin Bach <benjamin@overtag.dk> wrote:
> Arjan van de Ven wrote:
> > there are over a thousand open source drivers, and at most a handful
> > binary ones. Please go do your math.
> >
> You're doing the wrong comparison. How many drivers are missing or
> lacking in ability? And if you add to your handful of binary drivers
> those thousands that exist for xp...
> well, numbers do change. Also, most open source drivers aren't made by
> the vendors themselves.
>
> We're doing subjective math here. It doesn't change the fact that Linux
> would be better off with improved hardware support, right?
>

I strongly disagree.

Linux will be better off with improved hardware support by Open Source
drivers - yes.

With improved hardware support by closed source, binary only drivers,
Linux could very well end up being a *lot* worse off.

Once companies have the abillity to easily create closed drivers it
seems very likely that more of them will start withholding specs,
making it impossible to create open drivers.
This in turn will lead to less and less hardware supported by open
drivers. The result of this will be more and more useless bugreports
on LKML making it increasingly hard to maintain and improve the
kernel.  Users will report a bug that may or may not be in an open
part of the kernel, but it will be impossible to tell due to all the
binary only drivers for the users hardware she has loaded.
Binary drivers also put the stability and security of the users system
at the mercy of a commercial entity outside the users control.  A
binary blob loaded into the kernel could do *anything* to compromise
the system or cause it to become unstable and noone would be able to
tell if it's the driver or something else - Linux stability will
suffer and users will in many cases blame Linux, not the driver
vendors.

There's also the issue of companies going out of business, taking
their closed drivers with them. Now the hardware that used to be
supported by Linux is no longer useful since noone can keep the driver
updated.  One could then opt to keep the binary interfaces static to
keep old vendor drivers working, but then we'd quickly accumulate a
bunch of backwards compatibility cruft that would bloat the kernel and
turn it into an unmaintainable mess.

For users there will be a short term bennefit of having more new and
shiny toys work on Linux, but in the longer term it could easily
destroy the usefulness of Linux as a free Operating System.

So please, let's *not* do work to make binary only closed source
drivers easier to make or maintain, it's counterproductive in the long
run.


It's a lot like peeing in your pants to try and stay warm in a
blizzard. It may feel nice initially, but a little later on when your
legs freeze up you'll be a lot worse off than you were initially.


--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  parent reply	other threads:[~2006-03-18 16:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 18:00 Benjamin Bach
2006-03-17 17:49 ` Christoph Lameter
2006-03-17 18:35 ` Lee Revell
2006-03-18 15:03   ` Benjamin Bach
2006-03-18 15:10     ` Arjan van de Ven
2006-03-18 15:53       ` Benjamin Bach
2006-03-18 16:11         ` Arjan van de Ven
2006-03-19 10:47           ` Benjamin Bach
2006-03-19 11:54             ` Jesper Juhl
2006-03-19 15:19             ` Bob Copeland
2006-03-19 16:12               ` Benjamin Bach
2006-03-20 11:43                 ` Denis Vlasenko
2006-03-20 15:46                 ` Bob Copeland
2006-03-21 23:02                   ` Lee Revell
2006-03-22 21:51                   ` Pavel Machek
2006-03-18 16:12         ` Jesper Juhl [this message]
2006-03-18 16:51         ` Adrian Bunk
2006-03-19 16:30     ` Sander
2006-03-19 18:02   ` Nix

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=9a8748490603180812n1fda55bfq8909e118cc6dc3cc@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=arjan@infradead.org \
    --cc=benjamin@overtag.dk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®