From: Lee Revell <rlrevell@joe-job.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Benjamin Bach <benjamin@overtag.dk>, linux-kernel@vger.kernel.org
Subject: Re: Idea: Automatic binary driver compiling system
Date: Tue, 21 Mar 2006 18:02:50 -0500 [thread overview]
Message-ID: <1142982171.4532.183.camel@mindpipe> (raw)
In-Reply-To: <b6c5339f0603200746k3e817e9bmdc278764fe488a8c@mail.gmail.com>
On Mon, 2006-03-20 at 10:46 -0500, Bob Copeland wrote:
> On 3/19/06, Benjamin Bach <benjamin@overtag.dk> wrote:
> > Otherwise I'll probably dig up something. Just needs to be a small
> > kernel-whatever project.
> >
> > Is there someone maintaining a list of non-implemented ideas for kernel
> > features/drivers?
>
> Although neither of these are easy and you very well might not get
> anything done in three months, a couple of bits of hardware that I
> have for which there are incomplete/no drivers, and where the
> manufacturer refuses to give out specs are:
>
> - Ricoh MMC/SD controllers. The project to figure those out is at:
> http://mmc.drzeus.cx/wiki/Controllers/Ricoh/Frontreport
>
> - 3D for NVidia. I know many people would take an open but basic 3D
> driver over the fully featured binary one - many people already use
> the 2D 'nv' driver for that reason. Rudolf Cornelissen has reverse
> engineered various bits of it (though it may apply only to the
> geforce-1 era cards) over here:
> http://web.inter.nl.net/users/be-hold/BeOS/NVdriver/3dnews.html
>
Lots of people don't even need 3D but have to run nvidia's driver to get
multihead support, it seems this would be much easier than full 3D
implementation.
> You will find it's a whole lot easier to write drivers when you have
> specs though, and the resulting drivers will also be better. But
> depending on the scope of your project, you could definitely learn
> something either way.
>
> Another thing that would be a lot easier to accomplish in 3 months
> would be to write a userspace filesystem using FUSE for something that
> isn't ordinarily accessed by filesystems; for example currently you
> can mount remote machines over ssh, cameras that can talk to gphoto,
> tar archives, gmail, etc.
Another easy project if you have old sound cards lying around is to port
some of the old OSS drivers to ALSA (a list was posted on LKML a while
back). This probably will take from a weekend to a few weeks.
Lee
next prev parent reply other threads:[~2006-03-21 23:02 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 [this message]
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=1142982171.4532.183.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=benjamin@overtag.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=me@bobcopeland.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox