From: "Heater, Daniel (IndSys, GEFanuc, VMIC)" <Daniel.Heater@gefanuc.com>
To: "'Linux Kernel Mailing List'" <email@example.com>
Subject: Distributing drivers independent of the kernel source tree
Date: Thu, 26 Sep 2002 16:55:07 -0400 [thread overview]
Message-ID: <A9713061F01AD411B0F700D0B746CA6802FC14D6@vacho6misge.cho.ge.com> (raw)
For some time I have been trying to figure out how to distribute drivers
that are not part of the kernel source tree. The drivers that I am supplying
are open source (BSD license) but are for obscure hardware and/or not ready
for/may never be ready for inclusion in the kernel proper. Business being
what it is though, I have to get them to the customer yesterday.
I would like to know if there is a good way to distribute drivers separate
from the kernel source tree?
1. Supplying patches does not seem to be feasible because there are so many
kernel versions and trees to cover. I'm not in a position to tell my
customers to run version 2.4.xx-xx. They need to be able to use these
drivers with the kernel version they have in their production environment.
Instead, I try to make my driver work on all versions of kernel 2.4.x.
2. Assuming the kernel source is in /usr/src/linux is not always valid.
3. I currently use /usr/src/linux-`uname -r` to locate the kernel source
which is just as broken as method #2.
If no good method exists, would someone be willing to suggest a standard
which would allow distribution of drivers separate from the kernel tree?
next reply other threads:[~2002-09-26 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 20:55 Heater, Daniel (IndSys, GEFanuc, VMIC) [this message]
2002-09-26 21:08 ` Distributing drivers independent of the kernel source tree Arjan van de Ven
2002-09-26 21:41 ` Alan Cox
2002-09-26 21:48 ` Jeff Garzik
2002-09-26 22:03 ` J.A. Magallon
2002-09-27 12:40 ` jbradford
2002-09-27 12:48 ` Andreas Schwab
2002-09-27 13:08 ` jbradford
2002-09-30 21:35 ` Anders Gustafsson
2002-09-26 21:16 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-09-27 7:35 ` Arjan van de Ven
2002-09-26 21:55 Heater, Daniel (IndSys, GEFanuc, VMIC)
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).