From: Lee Revell <rlrevell@joe-job.com>
To: Benjamin Bach <benjamin@overtag.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Idea: Automatic binary driver compiling system
Date: Fri, 17 Mar 2006 13:35:08 -0500 [thread overview]
Message-ID: <1142620509.25258.53.camel@mindpipe> (raw)
In-Reply-To: <441AF93C.6040407@overtag.dk>
On Fri, 2006-03-17 at 19:00 +0100, Benjamin Bach wrote:
> Hi all,
>
> First off: I'm new on this list. I'm also new at starting projects.
> Anyways, I've decided on this idea for my first year computer science
> project. I have three months to set it off and definitely the whole
> thing would be released into the world afterwards.
>
> Second: I don't want opinions on the issue of making it easier for
> companies to create binary (pre-compiled) drivers. Yes, we all want more
> open source drivers. Of course.
Then let's end the thread here because this is the crux of ther issue -
no one WANTS it to be easier for vendors to ship binary drivers.
Linux will not change to accomodate vendors desire for binary drivers.
The vendors must adapt to Linux. End of story.
Lee
next prev parent reply other threads:[~2006-03-17 18:35 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 [this message]
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
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=1142620509.25258.53.camel@mindpipe \
--to=rlrevell@joe-job.com \
--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