From: David Chow <davidchow@shaolinmicro.com>
To: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux drivers management
Date: Tue, 07 Feb 2006 00:50:49 +0800 [thread overview]
Message-ID: <43E77E69.8050702@shaolinmicro.com> (raw)
In-Reply-To: <43E71F75.7000605@stud.feec.vutbr.cz>
> Please read Documentation/stable_api_nonsense.txt in your copy of
> Linux source.
I've read the document, I strongly disagree, because it is not relavant
to my question or to my original purpose of this question.
Putting the driver source code in the kernel source tree has nothing to
do with talking about a stable kernel API . Even you put the driver
sources into the main kernel tree, it will still need a lot of work to
port all drivers if the API changes. Driver sources can still host in a
different project (e.g. projects in sf.net) and maintain open-source and
om by the community, no difference than before
For different compile time options that affect data structures, this is
well known a bad idea . These types of techniques no longer allowed in
Java and other OO languages . Because I can simply say the code is not
portable. If really need a recompile and optimize, the distro vendor
should bare this, but according to the document, "As Linux supports a
larger number of different devices "out of the box" than any other
operating system" , do you think Linux should one day or some day grow
to 1TB source tree to include all possible drivers for all hw come from
the world? I don't see there is reason why a kernel or OS need to
include all the drivers for all the hardware. I don't think there is any
OS vendors on the market to capable to distribute all drivers integrity,
then the choice is to make a disabled Linux OS because of an OSV who has
only limited supporting resources to suppport and certify limited
hardware devices.
Please see my other email responded to Jes about the learning curve and
documentation issues of a Linux driver developer to pick up Linux skills.
regards,
David Chow
next prev parent reply other threads:[~2006-02-06 16:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 9:45 Linux drivers management David Chow
2006-02-06 10:05 ` Michal Schmidt
2006-02-06 16:50 ` David Chow [this message]
2006-02-06 16:55 ` Randy.Dunlap
2006-02-06 19:45 ` Alan Cox
2006-02-06 19:46 ` Jesper Juhl
2006-02-06 10:08 ` Jes Sorensen
2006-02-06 16:52 ` David Chow
2006-02-06 17:03 ` Pedro Alves
2006-02-06 17:35 ` Geert Uytterhoeven
2006-02-06 17:42 ` Jes Sorensen
2006-02-06 16:56 ` Christoph Hellwig
2006-02-07 11:36 ` Denis Vlasenko
2006-02-07 13:22 ` Christoph Hellwig
2006-02-06 19:51 ` Greg KH
2006-02-06 21:38 ` Jim Crilly
-- strict thread matches above, loose matches on Subject: below --
2006-02-06 18:31 Nicolas Mailhot
2006-02-06 18:56 ` Yaroslav Rastrigin
2006-02-06 19:02 ` Joshua Kugler
2006-02-06 19:17 ` Yaroslav Rastrigin
2006-02-06 19:39 ` Martin Mares
2006-02-06 19:56 ` Jan-Benedict Glaw
2006-02-06 19:53 ` Jan-Benedict Glaw
2006-02-06 20:04 ` Jesper Juhl
2006-02-06 23:52 ` Bernd Petrovitsch
2006-02-06 19:21 ` linux-os (Dick Johnson)
2006-02-06 19:46 ` Michael Krufky
2006-02-06 19:58 ` Nicolas Mailhot
2006-02-06 23:16 ` Gene Heskett
2006-02-06 19:30 Nicolas Mailhot
2006-02-07 4:42 linux
2006-02-07 16:18 ` Eric W. Biederman
2006-02-07 19:45 ` David Chow
2006-02-07 20:03 ` Kyle Moffett
2006-02-07 22:15 ` Theodore Ts'o
2006-02-08 0:52 ` David Chow
2006-02-08 4:02 ` Theodore Ts'o
2006-02-08 9:46 ` Bernd Petrovitsch
2006-02-09 6:09 ` Lee Revell
2006-02-08 1:06 ` Alan Cox
2006-02-08 8:26 ` Denis Vlasenko
2006-02-11 18:47 ` Andrew James Wade
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=43E77E69.8050702@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xschmi00@stud.feec.vutbr.cz \
/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