lkml.org 
[lkml]   [2001]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
On Thu, May 03, 2001 at 10:46:13PM +0800, Yiping Chen wrote:
> I want to contact with the author of linux kernel.
> Anybody knows how to contact with them?

"linux-kernel@vger.kernel.org" list is quite good way for that.

> Our leader hope put our own driver into linux kernel.
> I am not sure whether it was permitted.

It is even encouraged. As has been mentioned here before, each
Linux kernel source tarball (at least 2.4.* series) has file:

Documentation/SubmittingDrivers

which describes the method.


Of course we (the fuzzy thing called "user community") would prefer
to have nice sourcecode with lots of comments telling why something
is done in a way it is done, especially when it is a matter of poking
some lowlevel things in the hardware.

We see also highly obscured driver(s) appearing from various vendors,
which support some single spot revision(s) of kernel(s). This includes
binary-only drivers...

While vendors may have reasons not to publish some details of how to
drive their hardware, usually it only makes their hardware less attractive
for Linux users when the drivers are limited to i386 architecture and
only some very few kernels by given vendors.

While Linux kernels with even second number (2.4.* as an example)
will TRY TO maintain internal API consistent, even down to BINARY
format, that might not always be so.

Especially there exists a radical difference in between multiprocesor
kernels (SMP), and uniprocessor kernels. So radical that they are
binary incompatible. (This is configuration option before compiling
the kernel.) YOU (driver author) should always write SMP safe code
with spinlocks protecting access to codepaths/data-areas needing
consistent serialized access. Compilation will optimize away the
spinlocks in uniprocessor setups.


A well written driver is supplied in source, and is easily readable
by other people who need to go over the entire kernel for some subtle
detail changes over the next development phases (such has happened
before, and will likely happen again.)

A well written driver will very likely work at hardware with different
endianity than i386 architecture of PCs -- for example PowerPC machines.
(Of course core-logic drivers don't need to work anything but i386 PC,
but PCI interfaced peripheral gizmo can be used anywhere.)


> So, I need to contact with the authors of linux kernel.
> If you know how to do it, please tell me.
> Thanks!!
> Yiping Chen

/Matti Aarnio <matti.aarnio@zmailer.org>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:52    [W:0.064 / U:3.468 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site