All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Rychter <jan@rychter.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Centrino support
Date: Sat, 16 Aug 2003 12:58:35 -0700	[thread overview]
Message-ID: <m2isoxgys4.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: 20030816123410.56cbb550.skraw@ithnet.com

[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]

>>>>> "Stephan" == Stephan von Krawczynski <skraw@ithnet.com>:
 Stephan> On Fri, 15 Aug 2003 16:46:19 -0400
 Stephan> Brandon Stewart <rbrandonstewart@yahoo.com> wrote:

 >> I thought that this line of argument was due to FCC
 >> regulations. That is, software settings would allow the hardware to
 >> violate frequency or strength-of-signal limitations set by
 >> government regulations. This is only from memory, so feel free to
 >> correct.

 Stephan> I think I have read in an earlier thread something the like.
 Stephan> But I cannot understand how this can be logically linked to
 Stephan> releasing docs. If all companies would follow this thought
 Stephan> e.g. Siemens would never have released the docs for ISDN
 Stephan> chipsets and therefore no ISDN drivers would be in the
 Stephan> kernel. I'd rather say someone with money is afraid ...

Yes, that sounds rather ridiculous. Sooner or later someone is going to
reverse-engineer the thing, so not releasing drivers or specs just
delays this moment. If there's a manager at Intel that thinks this way,
he doesn't understand much about security.

[...]

 Stephan> Some political explosives are in this thread ...

Politically, this sounds to me like an antitrust case against Intel and
Microsoft handed on a platter. A major hardware manufacturer releases
information and software only to one dominating software company, while
locking out the others.

Unfortunately, we live in a world of compromises. If I were RedHat, I'd
stay real quiet and play nice in order to get Intel's cooperation on
servers (which brings revenue) instead of fighting for laptops (which is
a niche market for Linux, in a chicken-and-egg sort of way).

It's rather sad.

--J.

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2003-08-17 18:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15 18:13 Centrino support Jan Rychter
2003-08-15 18:29 ` Dave Jones
2003-08-15 18:33 ` Martin List-Petersen
2003-08-15 18:40 ` Bryan O'Sullivan
2003-08-15 20:24   ` Christian Axelsson
2003-08-15 20:35     ` Randy.Dunlap
2003-08-15 20:55     ` Bryan O'Sullivan
2003-08-15 21:22       ` Martin List-Petersen
2003-08-16 22:32         ` insecure
2003-08-17  4:16           ` Jamie Lokier
2003-08-15 20:35   ` Jan Rychter
2003-08-15 20:53     ` Bryan O'Sullivan
2003-08-16 19:58       ` Jan Rychter
2003-08-16 14:23     ` Dave Jones
2003-08-16 15:12     ` Alan Cox
2003-08-18 23:52       ` Rob Landley
2003-08-15 20:46   ` Brandon Stewart
2003-08-16 10:34     ` Stephan von Krawczynski
2003-08-16 19:58       ` Jan Rychter [this message]
2003-08-17 19:17         ` Jamie Lokier
2003-08-17 19:24         ` Alan Cox
2003-08-16 11:27     ` Tomas Szepe
2003-08-18  8:31     ` Helge Hafting
2003-08-19 21:15       ` James H. Cloos Jr.
2003-08-19 23:55         ` Jamie Lokier
2003-08-21 19:33           ` Micha Feigin
2003-08-17 20:07 ` Jussi Laako
  -- strict thread matches above, loose matches on Subject: below --
2003-08-15 20:32 Jean Tourrilhes
2003-08-15 22:36 Ricardo Galli

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=m2isoxgys4.fsf@tnuctip.rychter.com \
    --to=jan@rychter.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.