From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: What exactly does "supports Linux" mean?
Date: 13 May 2003 22:36:01 +0200 [thread overview]
Message-ID: <yw1x3cjifutq.fsf@zaphod.guide> (raw)
In-Reply-To: 200305131114_MC3-1-38B0-3C13@compuserve.com
Chuck Ebbert <76306.1226@compuserve.com> writes:
> > My general conclusion would be that something not working with a standard
> > kernel cannot be called "supporting linux", no matter what distros ever are
> > supported. You may call me purist...
>
> If their drivers don't come with full source code then their claims
> of supporting Linux are just a bad joke AFAIC.
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.
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-05-13 20:27 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 [this message]
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
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=yw1x3cjifutq.fsf@zaphod.guide \
--to=mru@users.sourceforge.net \
--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).