From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: What exactly does "supports Linux" mean?
Date: Wed, 14 May 2003 14:09:33 +0000 (UTC) [thread overview]
Message-ID: <b9timt$e3m$3@tangens.hometree.net> (raw)
In-Reply-To: yw1x3cjifutq.fsf@zaphod.guide
mru@users.sourceforge.net (=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=) writes:
>Even when they do, it's often far from what I would call "Linux
>support". I've seen vendor drivers that made such assumptions about
>the machine that they would only work on IA-32 machines. I'm talking
>about things like assuming that sizof(int) == sizeof(void *) == 4, or
>that physical memory addresses are the same seen from the CPU and from
>the PCI bus.
This is why "the other OS" has the WHQL, signs drivers and generally
does many things (including getting some cash from driver vendors) to
ensure (and enforce!) that the "designed for Windows xxx" logo really
helps customers.
And might be one of the reasons why they're releasing a new 'kernel'
version only once every two years and go through many pains to ensure,
that old drivers still run most of the times. This is an area where
Linux (and many of the Linux advocates) could really learn.
>From a user land perspective, only major Linux vendors or
organizations could enforce such a logo program, it would cost wads of
cash and it will really suck if you currently run the certification
process for Linux 2.5.102 for your driver and right before you're
done, 2.5.103 is released and you have to start all over again.
That's why most of the companies that _do_ provide drivers, provide
them for _one_ kernel release of some Linux distributions.
Heck, I was working with an IDS (won't tell you which one), which
shipped its security relevant kernel module _only_ for a truly well
known distribution with the stock kernel release which had remotely
exploitable holes.
While nVidia bashing is very popular on this list, this is one of the
few companies that, while distributing binary only drivers, try to
make an effort to keep their drivers reasonably up to date _and_ work
with most new kernel releases.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
next prev parent reply other threads:[~2003-05-14 13:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 15:12 What exactly does "supports Linux" mean? Chuck Ebbert
2003-05-13 20:36 ` Måns Rullgård
2003-05-14 2:12 ` jw schultz
2003-05-14 7:57 ` Riley Williams
2003-05-14 17:58 ` Måns Rullgård
2003-05-17 16:05 ` Pavel Machek
2003-05-18 1:39 ` jw schultz
2003-05-18 3:53 ` Werner Almesberger
2003-05-18 21:49 ` Pavel Machek
2003-05-18 22:20 ` Neale Banks
2003-05-19 10:20 ` Helge Hafting
2003-05-14 14:11 ` Henning P. Schmiedehausen
2003-05-14 15:29 ` Mike Dresser
2003-05-15 0:11 ` jw schultz
2003-05-14 14:09 ` Henning P. Schmiedehausen [this message]
2003-05-14 14:44 ` Dave Jones
2003-05-14 15:58 ` Henning Schmiedehausen
2003-05-14 16:14 ` Dave Jones
2003-05-14 19:40 ` David Schwartz
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 13:16 Stephan von Krawczynski
2003-05-13 12:53 ` Alan Cox
2003-05-13 14:24 ` Richard B. Johnson
2003-05-13 15:07 ` Lionel Bouton
2003-05-13 16:45 ` Jonathan Matthews
2003-05-13 13:46 ` Duncan Sands
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='b9timt$e3m$3@tangens.hometree.net' \
--to=hps@intermeta.de \
--cc=linux-kernel@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).