public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Brandon Stewart <rbrandonstewart@yahoo.com>
Cc: bos@serpentine.com, jan@rychter.com, linux-kernel@vger.kernel.org
Subject: Re: Centrino support
Date: Sat, 16 Aug 2003 12:34:10 +0200	[thread overview]
Message-ID: <20030816123410.56cbb550.skraw@ithnet.com> (raw)
In-Reply-To: <3F3D469B.2020507@yahoo.com>

On Fri, 15 Aug 2003 16:46:19 -0400
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.

I think I have read in an earlier thread something the like.
But I cannot understand how this can be logically linked to releasing docs. If
all companies would follow this thought e.g. Siemens would never have released
the docs for ISDN chipsets and therefore no ISDN drivers would be in the
kernel. I'd rather say someone with money is afraid ...
Mobile equipment like laptops is a booming market and it all turns around
shares...
There is another point about this topic. How does M$ (with their centrino
drivers) guarantee that no user tries to switch on the addtional ETSI
frequencies? I doubt this is possible at all. Of course you can simply ignore
that there are ETSI frequencies which basically means to ignore the
overwhelming part of europe and their respective regulation.
Some political explosives are in this thread ...

Regards,
Stephan


  reply	other threads:[~2003-08-16 10:34 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 [this message]
2003-08-16 19:58       ` Jan Rychter
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=20030816123410.56cbb550.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=bos@serpentine.com \
    --cc=jan@rychter.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rbrandonstewart@yahoo.com \
    /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