From: Jeff Garzik <jeff@garzik.org>
To: Stephen.Clark@seclark.us
Cc: James Ketrenos <jketreno@linux.intel.com>,
Axj <axjslack@bluebottle.com>,
linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] Request for help...
Date: Tue, 24 Jul 2007 21:35:09 -0400 [thread overview]
Message-ID: <46A6A8CD.9080806@garzik.org> (raw)
In-Reply-To: <46A69998.7020108@seclark.us>
Stephen Clark wrote:
> I find it really sad that a hardware vendor that is willing to write and
> develope drivers for Linux for their hardware aren't helped more by "the
> community"
It's hard to be more helpful without (a) explaining the problems with
the current situation and suggesting corrections, or (b) doing it all
myself.
> or is the "the community" only interested in hacking drivers where
> the manufacturer give no or minimal support?
The more people working on drivers, the wider the workload is spread,
which is a good thing.
The caveat being you cannot just throw any old crap into the kernel,
just because you are a Big Hardware Vendor. Linux thrives precisely
because of the system of engineering review and Internet-scale testing
that we have set up.
We have an engineering process that has proven itself over the past 10+
years. You don't just chuck that out the window because someone doesn't
want to follow the process. Making exceptions for Big Vendors who can't
grok the rules is not how Linux became successful.
These processes all have carefully considered engineering rationale
behind them. The obvious engineering breakdowns occur when you avoid
the standard process... the process that has been delivering stable
hardware support to you and other Linux users.
> I appreciate Intel's support for being open and purposely bought a
> laptop that had an Intel graphics chipset and an Intel wireless card.
Intel gets five stars in the areas of open source CPU, platform, and
graphics support. Intel graphics is really going to kick ass (not that
it doesn't already), and Keith Packard (old-school X11 hacker) is
leading the charge. And Intel networking definitely gets applause for
doing open source networking as well.
But we just don't shove any old vendor driver into the kernel. Not when
we have to maintain these drivers for a decade, often after the vendor
themselves end-of-life's the chip.
Jeff
next prev parent reply other threads:[~2007-07-25 1:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 15:02 Request for help Axj
2007-07-24 16:12 ` John W. Linville
2007-07-24 18:29 ` [ipw3945-devel] " Stephen Clark
2007-07-24 20:30 ` John W. Linville
2007-07-24 21:13 ` Jeff Garzik
2007-07-25 1:15 ` James Ketrenos
2007-07-25 0:03 ` Jeff Garzik
2007-07-25 0:30 ` Stephen Clark
2007-07-25 0:35 ` David Miller
2007-07-25 0:43 ` Stephen Clark
2007-07-25 0:46 ` David Miller
2007-07-25 1:05 ` Stephen Clark
2007-07-25 1:18 ` David Miller
2007-07-25 1:23 ` Jeff Garzik
2007-07-25 1:29 ` Stephen Clark
2007-07-25 1:40 ` Jeff Garzik
2007-07-25 1:40 ` Jeff Garzik
2007-07-25 0:45 ` Maurizio Monge
2007-07-25 1:35 ` Jeff Garzik [this message]
2007-07-25 8:01 ` James Ketrenos
2007-07-25 14:50 ` John W. Linville
2007-07-27 12:36 ` Jeff Garzik
2007-07-25 14:46 ` John W. Linville
2007-07-25 15:19 ` Jeff Garzik
2007-07-25 9:32 ` Zhu Yi
2007-07-26 15:10 ` Axj
2007-07-26 16:22 ` Pavel Roskin
2007-07-27 6:34 ` Axj
2007-07-27 7:44 ` Zhu Yi
2007-07-27 8:48 ` Axj
[not found] ` <200707270848.l6R8mqkh004526@mi1.bluebottle.com>
2007-07-27 8:56 ` Zhu Yi
2007-07-27 9:10 ` Axj
2007-07-30 0:58 ` Zhu Yi
2007-08-01 6:40 ` Axj
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=46A6A8CD.9080806@garzik.org \
--to=jeff@garzik.org \
--cc=Stephen.Clark@seclark.us \
--cc=axjslack@bluebottle.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jketreno@linux.intel.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).