From: Sander <sander@humilis.net>
To: Benjamin Bach <benjamin@overtag.dk>
Cc: Lee Revell <rlrevell@joe-job.com>, linux-kernel@vger.kernel.org
Subject: Re: Idea: Automatic binary driver compiling system
Date: Sun, 19 Mar 2006 17:30:30 +0100 [thread overview]
Message-ID: <20060319163030.GA15335@favonius> (raw)
In-Reply-To: <441C213A.3000404@overtag.dk>
Benjamin Bach wrote (ao):
> Linux get's better hardware support
With the help of binary drivers? Not likely. The smart people on this
list can't help for example.
> As of now Linux won't force vendors into creating open source drivers.
> That'd be like a small dog barking.
Well, as a customer you can put your money where your mouth is, and
simply buy other hardware. That is a way of forcing, or at least
stimulating the market.
As a kernel hacker you can choose to reverse engineer.
Btw, read this thread and tell me if you still agree that binary drivers
and depending on a company are a good thing:
http://forum.matrox.com/mga/viewtopic.php?t=19208&sid=724d14d42714800f9d13ee6286f37f0b
Kind regards, Sander
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2006-03-19 16:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 18:00 Idea: Automatic binary driver compiling system 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
2006-03-18 16:51 ` Adrian Bunk
2006-03-19 16:30 ` Sander [this message]
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=20060319163030.GA15335@favonius \
--to=sander@humilis.net \
--cc=benjamin@overtag.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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.