public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Bach <benjamin@overtag.dk>
To: linux-kernel@vger.kernel.org
Subject: Idea: Automatic binary driver compiling system
Date: Fri, 17 Mar 2006 19:00:28 +0100	[thread overview]
Message-ID: <441AF93C.6040407@overtag.dk> (raw)

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.

OK, so here goes: According to Distrowatch there's currently 377 
different distributions out. We have multiple architectures and fresh 
kernel patches every week. If we multiply these numbers, we'd find that 
a company wanting to release a closed-source driver module for Linux 
would face - say - 5,000 compilations a month. Impossible. So most 
companies just release largely incompatible binary drivers in a 
frustratingly limited variety.

I've been looking around for material about the topic of binary Linux 
drivers and creating such in a broad-scale batch mode. But I haven't 
found any. Oh yes, except for Documentation/stable_api_nonsens.txt which 
I found very helpful. But the issue is not having a stable interface - 
rather it is about having a good debugging and building tool that 
handles very very large amounts of kernel versions and patches.

I would be very grateful for pointers to any helpful resource and also 
thoughts on what problems I'm facing. Also I'm aware that this is 
probably not the first time "batch module compiling" has been mentioned... ?

Sincerely,
Benjamin Bach

             reply	other threads:[~2006-03-17 17:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 18:00 Benjamin Bach [this message]
2006-03-17 17:49 ` Idea: Automatic binary driver compiling system 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
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=441AF93C.6040407@overtag.dk \
    --to=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